aboutsummaryrefslogtreecommitdiffstats
path: root/doc/gpg.texi
diff options
context:
space:
mode:
authorWerner Koch <[email protected]>2025-02-03 10:46:57 +0000
committerWerner Koch <[email protected]>2025-02-03 10:46:57 +0000
commit4b2729b983bf3c6c1186ebdf1962f64d8cb1b3a1 (patch)
tree9295e022524bf05b554c2438e9db34bc1b2b88c7 /doc/gpg.texi
parentdoc: Record that gpg policy compliance options are last-one-wins (diff)
downloadgnupg-4b2729b983bf3c6c1186ebdf1962f64d8cb1b3a1.tar.gz
gnupg-4b2729b983bf3c6c1186ebdf1962f64d8cb1b3a1.zip
gpg: Simplify the compliance settings.
* g10/gpg.c (set_compliance_option): Base most settings on oGnuPG. For oGnuPG explictly clear the allow_old_cipher_algos flag. -- Note that --allow-old-cipher-algos must now come after a compliance settings. This avoids a bug when first setting oRFC2440 and then oGnuPG which would not clear the flag. GnuPG-bug-id: T7501
Diffstat (limited to 'doc/gpg.texi')
-rw-r--r--doc/gpg.texi4
1 files changed, 3 insertions, 1 deletions
diff --git a/doc/gpg.texi b/doc/gpg.texi
index fe2e5ce8c..9a621c89b 100644
--- a/doc/gpg.texi
+++ b/doc/gpg.texi
@@ -3687,7 +3687,9 @@ blocks of 64 bits; modern algorithms use blocks of 128 bit instead.
To avoid certain attack on these old algorithms it is suggested not to
encrypt more than 150 MiByte using the same key. For this reason gpg
does not allow the use of 64 bit block size algorithms for encryption
-unless this option is specified.
+unless this option is specified. Some compliance modes already set or
+clear this flag and thus this flags should be used after a compliance
+mode setting.
@item --allow-weak-digest-algos
@opindex allow-weak-digest-algos