Page MenuHome GnuPG
Create Task
Maniphest T2750

GOOD_PASSPHRASE has disappeared from status
Closed, InvalidPublic
Actions

Description

the GnuPG status code GOOD_PASSPHRASE appears to no longer be emitted by 2.1.15,
even though it was emitted by earlier versions of GnuPG.

I recognize that in the non-loopback pinentry mode, GOOD_PASSPHRASE isn't
necessarily meaningful (it would have to be reported by the agent anyway).

I'm seeing test suites in systems like request-tracker that expect to see a
password verification if they've supplied a --password-fd or something similar,
but no such status notification is returned to the caller of gpg. This seems
like an unfortunate regression -- how is a caller of gpg supposed to know
whether to look for such a status message or not? it is documented in DETAILS,
but doesn't appear to be actually used by the GnuPG code in 2.1.15.

But could

Details

Version
2.1.15

Related Objects

Event Timeline

dkg set Version to 2.1.15.Oct 12 2016, 2:34 PM
dkg added projects: gnupg, Bug Report.
dkg added a subscriber: dkg.
marcus closed this task as Invalid.Jul 24 2017, 7:22 PM
marcus added a subscriber: marcus.

The last time GOOD_PASSPHRASE was emitted was in 67934a8c1 (parent of 21b0a955) in 2010. I think that's just water down the river at this point.

dkg added a comment.Jul 28 2017, 12:01 AM

Yes, that commit was in 2010, but it was on the 2.1 branch, which never saw wide distribution until this year, which means that there are test suites (like the one mentioned in request-tracker) which simply fail hard when used against gpg 2.1. Is there explicit guidance that the GnuPG project wants to give to downstreams like request-tracker?

(PS in en_US we say "water under the bridge" -- interesting how the expressions are similar!)