Eliminate gpg-2comp default from gpg.el

Eliminate gpg-2comp default from gpg.el

[Florian Weimer]

The following patch removes the gpg-2comp default from gpg.el.
gpg-2comp is just another script to obtain, and nowadays, it's neither
recommended nor needed (it breaks OpenPGP compatibility, reduces
interoperability with GnuPG users etc.).  Catering for OpenPGP
implementations with known security defects should not be on our
agenda, either.

Okay to commit?

--- gpg.el.~1.16.~	Sun Aug 26 17:38:13 2001
+++ gpg.el	Wed Dec 26 12:05:03 2001
@@ -227,12 +227,12 @@
 
 (defcustom gpg-command-default-alist 
   '((gpg . "gpg")
-    (gpg-2comp . "gpg-2comp"))
+    (gpg-2comp . "gpg"))
   "Default paths for some GnuPG-related programs.
 Modify this variable if you have to change the paths to the
-executables required by the GnuPG interface.  You can enter \"gpg\"
-for `gpg-2comp' if you don't have this script, but you'll lose PGP
-2.6.x compatibility."
+executables required by the GnuPG interface.  You can enter \"gpg-2comp\"
+for `gpg-2comp' if you have obtained this script, in order to gain
+PGP 2.6.x compatibility."
   :tag "GnuPG programs"
   :type 'gpg-command-alist
   :group 'gpg-options)

Re: Eliminate gpg-2comp default from gpg.el

[Simon Josefsson]

Florian Weimer <fw@deneb.enyo.de> writes:

> The following patch removes the gpg-2comp default from gpg.el.
> gpg-2comp is just another script to obtain, and nowadays, it's neither
> recommended nor needed (it breaks OpenPGP compatibility, reduces
> interoperability with GnuPG users etc.).  Catering for OpenPGP
> implementations with known security defects should not be on our
> agenda, either.
>
> Okay to commit?

Please do, I always felt it was unnecessary.  Maybe the documentation
needs to be updated as well.

Re: Eliminate gpg-2comp default from gpg.el

[Florian Weimer]

Simon Josefsson <jas@extundo.com> writes:

> Florian Weimer <fw@deneb.enyo.de> writes:
>
>> The following patch removes the gpg-2comp default from gpg.el.
>> gpg-2comp is just another script to obtain, and nowadays, it's neither
>> recommended nor needed (it breaks OpenPGP compatibility, reduces
>> interoperability with GnuPG users etc.).  Catering for OpenPGP
>> implementations with known security defects should not be on our
>> agenda, either.
>>
>> Okay to commit?
>
> Please do, I always felt it was unnecessary.

Okay.

>  Maybe the documentation needs to be updated as well.

Which documentation? ;-) I've changed the introductory remarks, too,
and am not aware of any other documentation.

Re: Eliminate gpg-2comp default from gpg.el

[Simon Josefsson]

Florian Weimer <fw@deneb.enyo.de> writes:

>>  Maybe the documentation needs to be updated as well.
>
> Which documentation? ;-) I've changed the introductory remarks, too,
> and am not aware of any other documentation.

gpg-2comp is discussed in texi/gnus.texi, I'm not sure if the current
wording is correct.  Maybe that section could be extended into
something that isn't GPG specific?  There is some overlap between the
message manual and the Gnus manual.

Re: Eliminate gpg-2comp default from gpg.el

[Florian Weimer]

Simon Josefsson <jas@extundo.com> writes:

> gpg-2comp is discussed in texi/gnus.texi, I'm not sure if the current
> wording is correct.  Maybe that section could be extended into
> something that isn't GPG specific?  There is some overlap between the
> message manual and the Gnus manual.

I've removed the paragraph, it was incorrect anyway. The --rfc1991
GnuPG option still generates DES-encrypted messages, which can only be
read by a tweaked PGP 2.6.x version.  In addition, the --rfc1991 flag
does not take care of single-pass signature issues.