Page MenuHome GnuPG
Create Task
Maniphest T8338

Better error string for wrong passphrase
Open, Needs TriagePublic
Actions

Description

The error string for wrong passphrase is "Bad Passphrase" - but apparently we (want to) change it in the frontends to "Wrong passphrase" - shouldn't we fix it at the core instead?

Event Timeline

svuorela created this task.Thu, Jul 9, 11:57 AM
pl13 added a subscriber: pl13.Thu, Jul 9, 2:07 PM
• werner added a subscriber: • werner.Mon, Jul 13, 3:24 PM

Here is how we use the passphrase error codes:

11 = (0, 11) = (GPG_ERR_SOURCE_UNKNOWN, GPG_ERR_BAD_PASSPHRASE) = (Unspecified source, Bad passphrase)

    GNUPG: - The entered passphrase does not verify

31 = (0, 31) = (GPG_ERR_SOURCE_UNKNOWN, GPG_ERR_INV_PASSPHRASE) = (Unspecified source, Invalid passphrase)

    GNUPG:  - Required constraints of the passphrase are not met.

What is wrong with "bad" - In German we translate it to "Falsches Passwort" in Danish to "Ødelagt adgangsfrase"

svuorela added a comment.Tue, Jul 14, 8:51 AM

Both in Kleopatra and in Okular the BAD_PASSPHRASE gets converted to "Wrong passphrase" rather than just using the error string from gpg(me).

Also; The Danish translation is closer to "destroyed passphrase"