From: Michael Tremer <michael.tremer@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: GnuPG
Date: Mon, 29 Mar 2021 21:22:32 +0100 [thread overview]
Message-ID: <53CB769D-B282-4FBE-954E-99DF4275156D@ipfire.org> (raw)
In-Reply-To: <8cfdfabe-2734-3ded-cde6-6aef9032744a@ipfire.org>
[-- Attachment #1: Type: text/plain, Size: 1796 bytes --]
Hello,
As far as I know we do not use any exotic functionality.
The main (and maybe even only) user is pakfire, if that works we are fine. If that breaks, we are a bit screwed :)
-Michael
> On 27 Mar 2021, at 21:39, Adolf Belka <adolf.belka(a)ipfire.org> wrote:
>
> Hi Peter,
>
> On 27/03/2021 21:11, Peter Müller wrote:
>> Hello Adolf,
>> hello development folks,
>> sorry for my tardy reply.
> No problems. I know you have been and are very busy people.
>>> Is IPFire using the 1.4 Branch because there is some historic requirement for the older insecure keys.
>> (Assuming this was a question:) To my knowledge, we do not have key material in operation that would not
>> be supported by GnuPG 2.x - the "classic" branch simply is more lightweight than the 2.x branch.
>> The last time I looked at this, GnuPG 2.x required some flavour of the "pinentry" helper for entering
>> passphrases, and won't compile without. Since there is no manual interaction on a firewall, "pinentry"
>> is useless, but I was unable to work out how to omit it in GnuPG 2.x .
> Thanks for the heads up on this.
>> Things could have been changed, meanwhile. Perhaps this is now possible, so if you have some spare time
>> to look at this, go ahead. :-)
> I will give it a try. The worst that can happen is that I can't get it working and we stay with the status quo which is working currently.
>> Thank you very much in advance for your efforts - and all your patches of the last weeks.
> I am glad to help where I can.I know I can't help you with the real core stuff, my capabilities aren't sufficient but I can generally help with providing update patches on anything that I find has newer versions.
>
> Regards,
> Adolf
>
>> Thanks, and best regards,
>> Peter Müller
next prev parent reply other threads:[~2021-03-29 20:22 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-23 13:11 GnuPG Adolf Belka
2021-03-27 20:11 ` GnuPG Peter Müller
2021-03-27 21:39 ` GnuPG Adolf Belka
2021-03-29 20:22 ` Michael Tremer [this message]
2021-03-29 20:51 ` GnuPG Adolf Belka
2021-03-29 21:14 ` GnuPG Michael Tremer
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=53CB769D-B282-4FBE-954E-99DF4275156D@ipfire.org \
--to=michael.tremer@ipfire.org \
--cc=development@lists.ipfire.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox