'Re: Incompatible secret key format between 2.4.4 and 2.2.27?'

[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:       mlist_e9e869bc--- via Gnupg-users <gnupg-users () gnupg ! org>
Date:       2024-02-11 20:28:28
Message-ID: 0baca38e714308e190e28a4547faa0d9 () manycementmutable ! anonaddy ! com
[Download RAW message or body]

[Attachment #2 (multipart/alternative)]

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

[Attachment #5 (text/html)]

<!DOCTYPE html>
<html>
  <head>
    <meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
  </head>
  <body>
    <div class="moz-cite-prefix"><font face="monospace">On 11/02/2024
        18:09, IngoKlöcker 'kloecker at kde.org' wrote:<span
        style="white-space: pre-wrap">
</span></font></div>
    <blockquote type="cite" cite="mid:6021024.lOV4Wx5bFT@daneel">
      <pre class="moz-quote-pre" wrap="">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
</pre>
    </blockquote>
    <p><font face="monospace">Hello Ingo,</font></p>
    <p><font face="monospace">Thanks for the reply. It seems like the
        update I sent yesterday didn't went out. Apologize for being a
        noob on mailing list.</font></p>
    <p><font face="monospace">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.<br>
      </font></p>
    <p><font face="monospace">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.<br>
      </font></p>
    <p><font face="monospace">Regards,<br>
        Hartman<br>
      </font></p>
  </body>
</html>

_______________________________________________
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] 