diff options
author | Werner Koch <wk@gnupg.org> | 1998-12-14 21:22:42 +0100 |
---|---|---|
committer | Werner Koch <wk@gnupg.org> | 1998-12-14 21:22:42 +0100 |
commit | 7a7a5630aff7f539fd68de6c34d82a0fa240cc8c (patch) | |
tree | c0b8587dd3ef4e434ae03b043a52ad8ec645bc3f /doc/OpenPGP | |
parent | See ChangeLog: Sun Dec 13 14:10:56 CET 1998 Werner Koch (diff) | |
download | gnupg2-7a7a5630aff7f539fd68de6c34d82a0fa240cc8c.tar.xz gnupg2-7a7a5630aff7f539fd68de6c34d82a0fa240cc8c.zip |
See ChangeLog: Mon Dec 14 21:18:49 CET 1998 Werner Koch
Diffstat (limited to 'doc/OpenPGP')
-rw-r--r-- | doc/OpenPGP | 13 |
1 files changed, 1 insertions, 12 deletions
diff --git a/doc/OpenPGP b/doc/OpenPGP index 60fede3e0..1ae4fedf8 100644 --- a/doc/OpenPGP +++ b/doc/OpenPGP @@ -8,14 +8,10 @@ Compatibility Notes =================== - GnuPG (>=0.4.1) is in compliance with RFC2440 despite these exeptions: + GnuPG (>0.4.5) is in compliance with RFC2440 despite these exceptions: ===> Please can someone check this <========= - * (5.1) The critical bit in signature subpackets is currently - ignored. This will be fixed soon. - - * (5.2) GnuPG generates V4 signatures for all V4 keys. The option --force-v3-sigs allows to override. @@ -23,13 +19,6 @@ Encrypted Session-Key Packets"; however a warning message is issued if this option is active. - * (5.5.2) states that an implementaion MUST NOT create a v3 key - with an algorithm other than RSA. GnuPG has an option to - create an ElGamal key in a v3 packet; the properties of such - a key are as good as a v4 key. RFC1991 does not specifiy how - to create fingerprints for algorithms other than RSA and so it - is okay to choose a special format for ElGamal. - * (9.1) states that RSA SHOULD be implemented. This is not done (except with an extension, usable outside the U.S.) due to patent problems. |