--gnupg option

[David Shaw]

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

On Sat, Oct 11, 2003 at 07:57:06PM +0200, Kai Raven wrote:
> 
> Hi David,
> 
> On Sat, 11 Oct 2003 12:28:34 -0400 you wrote:
> 
> thx, very informative.
> 
> > - --gnupg:
> >   --force-v3-sigs
> 
> from the man:
> --force-v3-sigs
> --no-force-v3-sigs
> OpenPGP states that an implementation should generate v4 signatures but
> PGP versions 5 and higher only recognize v4 signatures on key material.
> 
> Do you know, which pgp versions have difficulties with v4 data
> signatures or is this refered to *all* versions up to PGP 8?

All versions before 7 cannot handle v4 data signatures.  Some versions
of 7 can handle them, and some can't.  8 can handle them.  I should
update the manual about that.

> 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.
>  
> So with --gnupg i cannot have an expiration date as with --openpgp or
> ask-sig-expire?

Correct.  You can do "--gnupg --no-force-v3-sigs" though.

> And what is with combinations like
> --openpgp --force-mdc

In GnuPG 1.2.3, --openpgp wins.  There would be no MDC.

> or
> --gnupg --no-force-v3-sigs

See above :)

Remember that --gnupg is the default.  You get --gnupg if you don't
explicitly set --openpgp, --rfc2440, --rfc1991, --pgp2, --pgp6,
- --pgp7, or --pgp8.

David
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.3.4-cvs (GNU/Linux)
Comment: Key available at http://www.jabberwocky.com/david/keys.asc

iHEEARECADEFAj+If38qGGh0dHA6Ly93d3cuamFiYmVyd29ja3kuY29tL2Rhdmlk
L2tleXMuYXNjAAoJEOJmXIdJ4cvJ1P4An1beZ7B2vFz2a/Tu/OnNHign8EhLAJ4z
rzQeCoWFW7JBhiuuWWPTN7NWmQ==
=JCIW
-----END PGP SIGNATURE-----