On Montag, 28. Oktober 2024 17:25:07 Mitteleuropäische Normalzeit Vincent Cozzo via Gnupg-users wrote: > I do have an update on this effort, though to make a long story short, > "the code works and I don't know why." > > When I try to install gpg 2.5.1 "system-wide," the executables end up > in /usr/local/bin. This sounds fine and normal, but in this state, I > encounter two problems: > 1. the prior error regarding "invalid public key alg" and even the > gpgconf error persist; > 2. when I try to do an `apt update`, the package manager gets confused > and says "Unknown error executing apt-key." Thankfully, I can remedy > this error by overwriting the /usr/local/bin executables with version > 2.4.5 of the library. > > if I try setting the GNUPGHOME variable (which is something I admit I > do not fully understand) and then copy the "pinentry" binaries to the > right directory, the system actually works and generates a Kyber key > -- and encryption/decryption appears to work when selecting that > subkey!
Maybe systemd gets in the way and starts a gpg-agent 2.4.5 which doesn't know anything about Kyber and therefore trying to create a key with your self- compiled gpg 2.5.1 fails. If you use a different GNUPGHOME then systemd's socket activation cannot get into the way. Usually gpg warns you if an older gpg-agent is running. So, unless you ignored this warning there's probably something else mixed up on your system. 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
