NO_SECKEY difference between 2.2 and 2.3

Ingo Klöcker kloecker at
Tue Nov 21 14:59:44 CET 2023

On Dienstag, 21. November 2023 12:05:39 CET Aleksander Machniak wrote:
> I just noticed a difference on how NO_SECKEY status is used between
> 2.2.x and 2.3.3.
> When I do --decrypt on an encrypted email message (having only
> recipient's private+public key in the keyring):
> - v2.2 outputs one NO_SECKEY line referring the recipient's key

Referring to the recipient's key? I understood that you do have the 
recipient's key but that you lack the sender's key.

> - v2.3 outputs two NO_SECKEY lines referring both recipient's and
> sender's keys.
> Is this expected behavior change?

Maybe not, but 2.3.3 is more than 2 years old. Current is 2.4.3.

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 228 bytes
Desc: This is a digitally signed message part.
URL: <>

More information about the Gnupg-users mailing list