Re: How to get a pubkey with WKD (Re: Incompatible secret key format between 2.4.4 and 2.2.27?)

2024-02-15 Thread Werner Koch via Gnupg-users
On Thu, 15 Feb 2024 11:48, Bernhard Reiter said: > But it does not get the current version of the pubkey in some circumstances. Example? I am not zware of it. > And the long version works in a few more elder GnuPG versions. ;) Since 2.2.17 from summer 2019 - 5 years passed since then with a

How to get a pubkey with WKD (Re: Incompatible secret key format between 2.4.4 and 2.2.27?)

2024-02-15 Thread Bernhard Reiter via Gnupg-users
Am Donnerstag 15 Februar 2024 10:45:53 schrieb Werner Koch: > The following will get his pubkey by WKD on the command line: > >  gpg  --locate-keys --auto-key-locate clear,nodefault,wkd w...@gnupg.org > > FWIW, > >   gpg --locate-external-key w...@gnupg.org > > is much easier that the abvove

Re: Incompatible secret key format between 2.4.4 and 2.2.27?

2024-02-15 Thread Werner Koch via Gnupg-users
On Wed, 14 Feb 2024 11:24, Bernhard Reiter said: > The following will get his pubkey by WKD on the command line: > gpg --locate-keys --auto-key-locate clear,nodefault,wkd w...@gnupg.org FWIW, gpg --locate-external-key w...@gnupg.org is much easier that the abvove long list of options.

Re: Incompatible secret key format between 2.4.4 and 2.2.27?

2024-02-14 Thread Bernhard Reiter via Gnupg-users
Am Dienstag 13 Februar 2024 15:50:55 schrieb mlist_e9e869bc--- via Gnupg-users: > Is wk at gnupg.org the private email I can send the public key to you? Yes, that is one of Werner's pubkeys. The following will get his pubkey by WKD on the command line: gpg --locate-keys --auto-key-locate

Re: Incompatible secret key format between 2.4.4 and 2.2.27?

2024-02-13 Thread mlist_e9e869bc--- via Gnupg-users
On 13/02/2024 09:57, Werner Koch 'wk at gnupg.org' wrote: > Can you please try to import that key (with the v5 key signature) using > a current 2.2. version (2.2.42)? Or you can send me the public key by > private mail so that I can check what's going on. > > > Salam-Shalom, > > Werner > I

Re: Incompatible secret key format between 2.4.4 and 2.2.27?

2024-02-13 Thread Werner Koch via Gnupg-users
On Sun, 11 Feb 2024 20:28, mlist_e9e869bc--- said: > signature is done in Version 5, instead of Version 4 like other parts of > the key. With that certify signature removed, I can import the secret > key to GPG 2.2.27 no problem. Can you please try to import that key (with the v5 key

Re: Incompatible secret key format between 2.4.4 and 2.2.27?

2024-02-11 Thread mlist_e9e869bc--- via Gnupg-users
On 11/02/2024 18:09, IngoKlöcker 'kloecker at kde.org' wrote: > Are you sure that the problem isn't the decryption? I checked the code and > this error message is emitted by the armor/dearmor code. My guess is that the > decryption fails and therefore outputs nothing and importing nothing results

Re: Incompatible secret key format between 2.4.4 and 2.2.27?

2024-02-11 Thread Ingo Klöcker
On Sonntag, 11. Februar 2024 02:05:52 CET mlist_e9e869bc--- via Gnupg-users wrote: > I'm trying to import a key generated from GPG 2.4.4 to 2.2.27 but > unsuccessful. > > Upon importing, it returns `gpg: no valid OpenPGP data found.` > > I tried with compliance options but it does nothing. > >