Yes, that makes sense. However, I do not know if I can use this keyring - in this state - to encrypt files?
Also, how ought I cleanup these old, unused keys? ~ Mike On Fri, Oct 4, 2024 at 2:23 AM Werner Koch <w...@gnupg.org> wrote: > Hi! > > You should not update to a 3 years old devel version. The current > stable version is 2.4.5. > > > gpg: DBG: Oops: keyid_from_fingerprint: no pubkey; fpr: > > 5d5ddc60954d5b06fa7b592ec45b70d9 > > That is a PGP-2 key. Support for them has been dropped in version 2.1.0 > (2014): > > * gpg: All support for v3 (PGP 2) keys has been dropped. All > signatures are now created as v4 signatures. v3 keys will be > removed from the keyring. > > See also https://gnupg.org/faq/whats-new-in-2.1.html > > If you still have data encrypted to such keys, you need to install GnuPG > 1.4. > > In the wake of the Snowden revelation there was a heavy move to newer > algorithms and thus PGP-2 was considered broken by some people. In fact > Google people heavily pledged for removing all support for PGP-2 for > GnuPG. Meanwhile I think this was the wrong decision - keeping PGP-2 > decryption capabilities would have been easier than all the extra code > to skip PGP-2 keys in existing keyrings. And of course the PGP-2 > encryption has not been broken - only signatures are vulnerable to the > full MD5 hash algorithm attacks we know for 25 years. > > > > Shalom-Salam, > > Werner > > -- > The pioneers of a warless world are the youth that > refuse military service. - A. Einstein > -- If ever I can be of service to you; contact me at once. I wish for you a truly extraordinary day ... -- Best Regards, Mike Schleif 612-235-6060 https://mikeschleif.net http://mdsresource.net http://www.linkedin.com/in/schleif http://facebook.com/MDSResource http://twitter.com/mikeschleif
_______________________________________________ Gnupg-users mailing list Gnupg-users@gnupg.org https://lists.gnupg.org/mailman/listinfo/gnupg-users
