[prev in list] [next in list] [prev in thread] [next in thread]
List: gnupg-users
Subject: Re: Incompatible secret key format between 2.4.4 and 2.2.27?
From: Ingo =?ISO-8859-1?Q?Kl=F6cker?= <kloecker () kde ! org>
Date: 2024-02-11 18:08:10
Message-ID: 6021024.lOV4Wx5bFT () daneel
[Download RAW message or body]
[Attachment #2 (multipart/signed)]
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 <key_id> | gpg -a -c
> --cipher-algo AES --force-mdc -o <file>`
> - 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" (application/pgp-signature)]
_______________________________________________
Gnupg-users mailing list
Gnupg-users@gnupg.org
https://lists.gnupg.org/mailman/listinfo/gnupg-users
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic