From: Adolf Belka <adolf.belka@ipfire.org>
To: development@lists.ipfire.org
Subject: GnuPG
Date: Tue, 23 Mar 2021 14:11:23 +0100 [thread overview]
Message-ID: <bf6172ba-7157-7a6a-a47c-a7cac2270fd9@ipfire.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 822 bytes --]
Hi All,
I was looking at GnuPG and it seemed very old to me. Then I realised it was on the Classic Branch 1.4. Reading about this branch, it is still getting security updates (last in 2018) but its purpose is said to be to support people who have archives of documents, messages, etc that are signed by old PGP keys that are no longer supported in the Modern Branch 2.x.. Hence 1.4 is required to be able to decrypt them.
Is IPFire using the 1.4 Branch because there is some historic requirement for the older insecure keys.
If yes, or there is some other reason that means IPFire should stay on 1.4 then I will leave GnuPG alone.
If no then I would have a go at updating GnuPG to the 2.2 Branch that is current.
I will wait to hear your feedback on this before doing anything.
Regards,
Adolf.
next reply other threads:[~2021-03-23 13:11 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-23 13:11 Adolf Belka [this message]
2021-03-27 20:11 ` GnuPG Peter Müller
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=bf6172ba-7157-7a6a-a47c-a7cac2270fd9@ipfire.org \
--to=adolf.belka@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