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

Atom 'Smasher' atom-gpg at suspicious.org
Sat Apr 10 08:59:16 CEST 2004


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

> 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.


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.


        ...atom

 _________________________________________
 PGP key - http://atom.smasher.org/pgp.txt
 3EBE 2810 30AE 601D 54B2 4A90 9C28 0BBF 3D7D 41E3
 -------------------------------------------------

	"The incidence of disease has increased
	 in proportion to the progress of science."
		-- Akbarali Jetha
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (FreeBSD)
Comment: What is this gibberish?  -  http://atom.smasher.org/links/#digital_signatures

iD8DBQFAd5tInCgLvz19QeMRAgLvAJwMb+E/FbknynA9/HxoYfnVgQrhoACfcI56
tRr4LQXNwcB1pqLCzeA8bH8=
=X+/o
-----END PGP SIGNATURE-----



More information about the Gnupg-users mailing list