gpg: can't put a policy URL into v3 (PGP 2.x style) signature
John A. Martin
jam at athene.jamux.com
Sat Apr 10 21:37:10 CEST 2004
>>>>> "Atom" == Atom
>>>>> "Re: gpg: can't put a policy URL into v3 (PGP 2.x style) signature"
>>>>> Sat, 10 Apr 2004 14:33:04 -0400 (EDT)
>> > > 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?
Atom> logic dictates that these statements can not both be
Atom> * "No version of PGP before 8 can reliably handle v4
Atom> -- dshaw
Atom> * "PGP versions 5 through 7 only recognize v4 signatures on
Atom> key material."
Atom> -- gpg (1.2.4) man page
... PGP versions 5 through 7 recognize v4 signatures only on
be more readily understood?
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Size: 154 bytes
Desc: not available
Url : /pipermail/attachments/20040410/81a87c3a/attachment.bin
More information about the Gnupg-users