[prev in list] [next in list] [prev in thread] [next in thread] 

List:       gnupg-users
Subject:    NO_SECKEY difference between 2.2 and 2.3
From:       Aleksander Machniak <alec () alec ! pl>
Date:       2023-11-21 11:05:39
Message-ID: 9564dbe1-059d-4084-a9c0-15a46141e61c () alec ! pl
[Download RAW message or body]

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
- v2.3 outputs two NO_SECKEY lines referring both recipient's and 
sender's keys.

Is this expected behavior change?

-- 
Aleksander Machniak
Kolab Groupware Developer        [https://kolab.org]
Roundcube Webmail Developer  [https://roundcube.net]
----------------------------------------------------
PGP: 19359DC1 # Blog: https://kolabian.wordpress.com

_______________________________________________
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