gpg: can't put a policy URL into v3 (PGP 2.x style) signature

David Shaw dshaw at
Sat Apr 10 13:00:17 CEST 2004

On Sat, Apr 10, 2004 at 02:59:16AM -0400, Atom 'Smasher' wrote:
> > PGP compatibility.  No version of PGP before 8 can reliably handle v4
> > signatures.
> =======================
> then this looks like a typo in the man page...
> 	--force-v3-sigs
> 	--no-force-v3-sigs
> 		OpenPGP states that an implementation should generate v4 sig-
> 		natures but PGP versions 5 through 7 only recognize v4 signa-
> 		tures on key material.  This option forces v3 signatures  for
> 		signatures  on  data.  Note that this option overrides --ask-
> 		sig-expire, as v3 signatures cannot  have  expiration  dates.
> 		--no-force-v3-sigs disables this option.

Where is the typo?

> also, this seems like a deviation from the usual behavior, that if there's
> a "--force-xyz" and a "--no-force-xyz", the "--no-force-xyz" is usually
> the default, unless otherwise specified.

The default is just the one that is most appropriate.  There is no
standard behavior to have the "no" value be the default.  Note
"--escape-from", "--mangle-dos-filenames", and "--ask-cert-level" are
also default-to-yes.


More information about the Gnupg-users mailing list