[prev in list] [next in list] [prev in thread] [next in thread]
List: gnupg-users
Subject: Re: NO_SECKEY difference between 2.2 and 2.3
From: Ingo =?ISO-8859-1?Q?Kl=F6cker?= <kloecker () kde ! org>
Date: 2023-11-21 13:59:44
Message-ID: 5733125.DvuYhMxLoT () daneel
[Download RAW message or body]
[Attachment #2 (multipart/signed)]
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.
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