On Dienstag, 23. August 2022 10:44:52 CEST theaetetos--- via Gnupg-users wrote: > Aug 22, 2022, 21:07 by kloec...@kde.org: > >> gpg2 --version > >> > >> >gpg (GnuPG) 2.3.3 > >> >libgcrypt 1.9.4 > > > > The solution is easy: Use gpg 2.3.7. > > Are you sure this should suffice?
Yes, I'm pretty sure. I followed your steps in a fresh GNUPGHOME and didn't see the warning message. I didn't protect the test keys with a passphrase though. I'm using openSUSE Tumbleweed. $ gpg --version gpg (GnuPG) 2.3.7 libgcrypt 1.9.4-unknown Or have I accidentally used $ gpg --version gpg (GnuPG) 2.3.8-beta28 libgcrypt 1.11.0 NOTE: THIS IS A DEVELOPMENT VERSION! ? I'm not sure. I intended to test with the distro versions. Regards, Ingo
signature.asc
Description: This is a digitally signed message part.
_______________________________________________ Gnupg-users mailing list Gnupg-users@gnupg.org https://lists.gnupg.org/mailman/listinfo/gnupg-users
