--pgp2 option

[David Shaw]

--J2SCkAp4GZ/dPZZf
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Sat, Nov 24, 2001 at 08:58:22AM -0800, Rich Wales wrote:
> David Shaw wrote:
>=20
>     > General question for the group: is it better to warn,
>     > rather than prevent the user from doing something that
>     > will blow up PGP2?
>=20
> I'd prefer to see the 2048-bit key length limit removed.  Some people
> use longer RSA keys (with modified versions of PGP2 that support such
> keys), and they should not be arbitrarily prevented from using GnuPG
> (or induced to create custom-modified versions of GnuPG).

The pgp2 patch doesn't prevent a PGP 2 user from using GnuPG.  All it
does is pre-set the various options to be PGP 2-compatible, and
prevent them from generating a message that would break PGP 2.

Anyone is free to use --cipher-algo, --digest-algo, --rfc1991, etc, to
generate the same exact messages.

I do know there are around a zillion variations of "PGP 2", but a
message prepared for the baseline MIT PGP 2.6.2 will work with all of
the variations.

David

--=20
   David Shaw  |  dshaw@jabberwocky.com  |  WWW http://www.jabberwocky.com/
+--------------------------------------------------------------------------=
-+
   "There are two major products that come out of Berkeley: LSD and UNIX.
      We don't believe this to be a coincidence." - Jeremy S. Anderson

--J2SCkAp4GZ/dPZZf
Content-Type: application/pgp-signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.6b (GNU/Linux)

iQEVAwUBO//aN4ccwqs8s7QVAQEGlQgAmh/9Jtm5jNE4S7K4CIU/SHnksciaefQd
9NK2aNCmQxJHxZvswhYce1x7MWLoEjNJmAD/flm2e2s6UOIRARtQqcSY7HrbNIKi
/tFuAk8QCllYwmhYkZGexnK24PODKYrPdFZ+Q52P6T4WAoS7evQVAOh8uBPiZx8v
Q4l8tpvbWelYc6whRx11N/1xo3xDeYQobFK7yf71bwCS+K5wAjOcUfDtqkKFmLcB
pI8vkrR3shBXf03xNghq53o/aU+G/tb/jsG1gPaQBPSwGzWDQozcMwXjXYzCs5oL
e/9r1cxEwt9UOmIYxzWdsbtNebKwyQE+NLYhy9jZ8AevMuxSt1x21Q==
=Sqy+
-----END PGP SIGNATURE-----

--J2SCkAp4GZ/dPZZf--