[svn] GnuPG - r4609 - trunk/doc

svn author dshaw cvs at cvs.gnupg.org
Fri Oct 26 06:16:51 CEST 2007


Author: dshaw
Date: 2007-10-26 06:16:42 +0200 (Fri, 26 Oct 2007)
New Revision: 4609

Modified:
   trunk/doc/ChangeLog
   trunk/doc/gpg.texi
Log:
* gpg.texi: Clarify --force-v3-sigs, --pgp2, and --pgp6 a bit.


Modified: trunk/doc/ChangeLog
===================================================================
--- trunk/doc/ChangeLog	2007-10-25 09:06:21 UTC (rev 4608)
+++ trunk/doc/ChangeLog	2007-10-26 04:16:42 UTC (rev 4609)
@@ -1,3 +1,7 @@
+2007-10-25  David Shaw  <dshaw at jabberwocky.com>
+
+	* gpg.texi: Clarify --force-v3-sigs, --pgp2, and --pgp6 a bit.
+
 2007-10-23  Werner Koch  <wk at g10code.com>
 
 	* tools.texi (Listing global options): New.

Modified: trunk/doc/gpg.texi
===================================================================
--- trunk/doc/gpg.texi	2007-10-25 09:06:21 UTC (rev 4608)
+++ trunk/doc/gpg.texi	2007-10-26 04:16:42 UTC (rev 4609)
@@ -1845,16 +1845,15 @@
 the type of the signature.
 @end ifset
 
-
-
 @item --force-v3-sigs
 @itemx --no-force-v3-sigs
 OpenPGP states that an implementation should generate v4 signatures
 but PGP versions 5 through 7 only recognize v4 signatures on key
 material. This option forces v3 signatures for signatures on data.
-Note that this option overrides @option{--ask-sig-expire}, as v3 signatures
-cannot have expiration dates. @option{--no-force-v3-sigs} disables this
-option.
+Note that this option overrides @option{--ask-sig-expire},
+ at option{--sig-policy-url}, @option{--sig-notation}, and
+ at option{--sig-keyserver-url}, as these features cannot be used with v3
+signatures.  @option{--no-force-v3-sigs} disables this option.
 
 @item --force-v4-certs
 @itemx --no-force-v4-certs
@@ -1975,11 +1974,10 @@
 2.x' here means `MIT PGP 2.6.2'. There are other versions of PGP 2.x
 available, but the MIT release is a good common baseline.
 
-This option implies @option{--rfc1991 --disable-mdc --no-force-v4-certs
---no-sk-comment --escape-from-lines --force-v3-sigs --no-ask-sig-expire
---no-ask-cert-expire --cipher-algo IDEA --digest-algo MD5
---compress-algo 1}. It also disables @option{--textmode} when
-encrypting.
+This option implies @option{--rfc1991 --disable-mdc
+--no-force-v4-certs --no-sk-comment --escape-from-lines
+--force-v3-sigs --cipher-algo IDEA --digest-algo MD5 --compress-algo
+ZIP}. It also disables @option{--textmode} when encrypting.
 
 @item --pgp6
 @opindex pgp6
@@ -1991,7 +1989,7 @@
 does not understand signatures made by signing subkeys.
 
 This option implies @option{--disable-mdc --no-sk-comment
---escape-from-lines --force-v3-sigs --no-ask-sig-expire}.
+--escape-from-lines --force-v3-sigs}.
 
 @item --pgp7
 @opindex pgp7
@@ -2709,10 +2707,11 @@
 of the standard, such as the SHA-512 hash, and the ZLIB and BZIP2
 compression algorithms. It is important to be aware that not all
 OpenPGP programs implement these optional algorithms and that by
-forcing their use via the @option{--cipher-algo}, @option{--digest-algo},
- at option{--cert-digest-algo}, or @option{--compress-algo} options in GnuPG, it is
-possible to create a perfectly valid OpenPGP message, but one that
-cannot be read by the intended recipient.
+forcing their use via the @option{--cipher-algo},
+ at option{--digest-algo}, @option{--cert-digest-algo}, or
+ at option{--compress-algo} options in GnuPG, it is possible to create a
+perfectly valid OpenPGP message, but one that cannot be read by the
+intended recipient.
 
 There are dozens of variations of OpenPGP programs available, and each
 supports a slightly different subset of these optional algorithms.




More information about the Gnupg-commits mailing list