- User Since
- Oct 6 2017, 1:20 PM (322 w, 3 d)
Dec 23 2021
Will go into 2.3.4.
Dec 19 2021
Okay, sorry. In the first two cases (encryption), GnuPG 2.2.33 generates
[GNUPG:] INV_RECP 10 F3C987C36C5C6343C9A5D5A1A3F494F6028E4866 [GNUPG:] FAILURE encrypt 53 gpg: [stdin]: encryption failed: Unusable public key
and exits with error code 2, whereas 2.2.32 doesn't display these messages and exits with return code 0.
Aug 20 2021
Oct 6 2017
Is this not a regression, rather than a new feature request? Earlier versions of GnuPG report sec rather than pub for such keys. The file itself is a private key - that it contains a public part is surely secondary in this context.