Page MenuHome GnuPG

In -de-vs mode it is not possible so verify sigs with Ed25519 release keys.
Closed, ResolvedPublic


This is a practical problem for customers of GnuPG VS-Desktop, where the compliance mode is globally configured.

gpg should not bail out here but verify the signature and print a notice. For script compatibility an extra option might be useful.

Event Timeline

werner created this task.
werner created this object with edit policy "Contributor (Project)".

Wouldn't it be safer to use gpgv for verifying the signature than to add a code path to gpg to circumvent the hard de-vs compliance check?

werner claimed this task.

Yes, but it is more complicated to do because you need to download a binary version of the keys and check that they are authentic. Most users don't known it. Anyway, I meanwhile created a Brainpool release sign key and new VSD releases are signed with that. The override option does not really harm, but we can close this bug due to the new release key.

The introduction of --override-compliance-check actually hid the real
cause for the signature verification problem in de-vs mode for the
Ed25519 key. The real fix is to handle the EdDSA algorithm in

Fixed for 2.2.42 and 2.4.1.

ebo moved this task from Restricted Project Column to Restricted Project Column on the Restricted Project board.Jul 24 2023, 2:12 PM