public inbox for development@lists.ipfire.org
 help / color / mirror / Atom feed
From: "Peter Müller" <peter.mueller@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: GnuPG
Date: Sat, 27 Mar 2021 21:11:25 +0100	[thread overview]
Message-ID: <ac34dbd7-9482-edab-a8b6-dd6b0368bc44@ipfire.org> (raw)
In-Reply-To: <bf6172ba-7157-7a6a-a47c-a7cac2270fd9@ipfire.org>

[-- Attachment #1: Type: text/plain, Size: 941 bytes --]

Hello Adolf,
hello development folks,

sorry for my tardy reply.

> 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 .

Things could have been changed, meanwhile. Perhaps this is now possible, so if you have some spare time
to look at this, go ahead. :-)

Thank you very much in advance for your efforts - and all your patches of the last weeks.

Thanks, and best regards,
Peter Müller

  reply	other threads:[~2021-03-27 20:11 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 ` Peter Müller [this message]
2021-03-27 21:39   ` GnuPG Adolf Belka
2021-03-29 20:22     ` GnuPG Michael Tremer
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=ac34dbd7-9482-edab-a8b6-dd6b0368bc44@ipfire.org \
    --to=peter.mueller@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