Re: Incompatible secret key format between 2.4.4 and 2.2.27?
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 > exactly in the above error message: > ``` > $ echo "" | gpg --import - > gpg: no valid OpenPGP data found. > gpg: Total number processed: 0 > ``` > > Regards, > Ingo Hello Ingo, Thanks for the reply. It seems like the update I sent yesterday didn't went out. Apologize for being a noob on mailing list. The problem is in the certify signature. For some reason a certify 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. Now the unrelated decryption. It actually decrypt nicely to an armoured PGP private key block. However, it just not importable even with GPG 2.4.4. I guess the data with in is corrupted but no way to verify. Regards, Hartman ___ Gnupg-users mailing list Gnupg-users@gnupg.org https://lists.gnupg.org/mailman/listinfo/gnupg-users
Re: Incompatible secret key format between 2.4.4 and 2.2.27?
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. > > Command I used: > > - export: `gpg -a --export-secret-subkey | gpg -a -c > --cipher-algo AES --force-mdc -o ` > - import: `gpg --decrypt -o - keys.sec.asc | gpg --import -` > > What else I can do? I can't update the GPG version because one of my > import device is an Android phone which stuck at 2.2.27 for quite a long > time. 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 exactly in the above error message: ``` $ echo "" | gpg --import - gpg: no valid OpenPGP data found. gpg: Total number processed: 0 ``` 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
