mirror of
git://git.gnupg.org/gnupg.git
synced 2025-02-01 16:33:02 +01:00
gpg: Allow to create revocations even with non-compliant algos.
* g10/sign.c (do_sign): Skip compliance check for revocation certs. -- It just does not make sense to inhibit the creation of revocations depending on the compliance mode. We do this only for key revocation but not for another kind of revocation because the rationale for uid or subkey revocation is more complicated to explain.
This commit is contained in:
parent
6400672904
commit
89c7eccba5
12
g10/sign.c
12
g10/sign.c
@ -385,8 +385,9 @@ do_sign (ctrl_t ctrl, PKT_public_key *pksk, PKT_signature *sig,
|
||||
goto leave;
|
||||
}
|
||||
|
||||
/* Check compliance. */
|
||||
if (! gnupg_digest_is_allowed (opt.compliance, 1, mdalgo))
|
||||
/* Check compliance but always allow for key revocations. */
|
||||
if (!IS_KEY_REV (sig)
|
||||
&& ! gnupg_digest_is_allowed (opt.compliance, 1, mdalgo))
|
||||
{
|
||||
log_error (_("digest algorithm '%s' may not be used in %s mode\n"),
|
||||
gcry_md_algo_name (mdalgo),
|
||||
@ -395,9 +396,10 @@ do_sign (ctrl_t ctrl, PKT_public_key *pksk, PKT_signature *sig,
|
||||
goto leave;
|
||||
}
|
||||
|
||||
if (! gnupg_pk_is_allowed (opt.compliance, PK_USE_SIGNING,
|
||||
pksk->pubkey_algo, 0,
|
||||
pksk->pkey, nbits_from_pk (pksk), NULL))
|
||||
if (!IS_KEY_REV (sig)
|
||||
&& ! gnupg_pk_is_allowed (opt.compliance, PK_USE_SIGNING,
|
||||
pksk->pubkey_algo, 0,
|
||||
pksk->pkey, nbits_from_pk (pksk), NULL))
|
||||
{
|
||||
log_error (_("key %s may not be used for signing in %s mode\n"),
|
||||
keystr_from_pk (pksk),
|
||||
|
Loading…
x
Reference in New Issue
Block a user