Page MenuHome GnuPG
Feed Advanced Search

Advanced Search
Use Results
Hide Query

Dec 23 2021

vsajip added a comment to T5742: Apparent regressions between 2.2.32 and 2.2.33 of GnuPG.

Will go into 2.3.4.

Dec 23 2021, 12:13 PM · Restricted Project, Bug Report, gnupg (gpg23)

Dec 19 2021

vsajip updated the task description for T5742: Apparent regressions between 2.2.32 and 2.2.33 of GnuPG.
Dec 19 2021, 8:04 PM · Restricted Project, Bug Report, gnupg (gpg23)
vsajip added a comment to T5742: Apparent regressions between 2.2.32 and 2.2.33 of GnuPG.

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.

Dec 19 2021, 7:59 PM · Restricted Project, Bug Report, gnupg (gpg23)
vsajip renamed T5742: Apparent regressions between 2.2.32 and 2.2.33 of GnuPG from Apparent regressions between 2.2.30 and 2.2.33 of GnuPG to Apparent regressions between 2.2.32 and 2.2.33 of GnuPG.
Dec 19 2021, 3:18 PM · Restricted Project, Bug Report, gnupg (gpg23)
vsajip created T5742: Apparent regressions between 2.2.32 and 2.2.33 of GnuPG.
Dec 19 2021, 2:33 PM · Restricted Project, Bug Report, gnupg (gpg23)

Aug 20 2021

vsajip created T5562: GnuPG behaves inconsistently across versions when a secret key is not found during decryption.
Aug 20 2021, 11:05 PM · Bug Report, gnupg (gpg23)

Oct 6 2017

vsajip added a comment to T3431: Private key reported as public.

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.

Oct 6 2017, 1:26 PM · Feature Request