HOWTO on interfacing with gnupg/pgp?

Pedro Díaz Jiménez pdiaz88@terra.es
Mon Jun 18 21:07:02 2001


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

Hi,
On Monday 18 June 2001 17:57, Werner Koch wrote:

> || On Mon, 18 Jun 2001 18:58:17 +0000
> || Pedro Díaz Jiménez <pdiaz88@terra.es> wrote:
>
> pdj> any pattented algoritms in gnupg, but lets face it. Sometimes, some
> of us pdj> have to use them (one of my teachers uses pgp 2.x). and patching
> gnupg pdj> sources doesn't seem clear to me. Does gnupg support any kind of
> plugin
>
> You want to trade in usability for freedom. The GNU project does not
> do this.
No I don't!. I just wanna let the user do this trade if he/she wants/needs.
>
> One of the reasons for the plugin code in GnuPG is that the IDEA and RSA
> patent are not valid in all countries (especially RSA) and therefore we
> wanted
> to allow users in those countries to be able to use these algorithms
> and more easily replace their proprietary PGP[1] with Free Software. It
> was a pitty that this was not possible for most users. Since Sep 20th 2000
> there is no more reason for using PGP because the RSA patent expired.
> There is almost no reason to use IDEA anymore because we have other
> algorithms which are at least as strong as IDEA.
>
> And it is a good idea to adhere to standards. PGP 2 is not OpenPGP
> compliant and has a few security weaknesses.
>
> By still using IDEA you are giving the proponents of software patents
> a momentum - we have to fight software patents and if it is
> only[1] to protect our Free Software.
>
I agree. Software patents are evil
> So please don't expect from a GNU project that it will ever support
> proprietary software.
Thats a little drastic, don't your think?. Take a look out there. There's a whole bunch of GPL'd programs that support propietary software. Abiword opens .doc files (more or less). xmms plays .mp3 files. Gimp edits .gif files. The linux kernel supports a wide variety of propietary filesystems . . and so on... the reason that abiword can open .doc files is not because they think its the better format out there. They do it because they are flexible. More or less occurs with the other examples. They say: ''hey, we don't like it, but we can also do that.". Anyway, I understand your point of view. As the gnupg user base grows, it will become more and more the 'de facto' standard, implicity promoting the use of non-pattented algoritms. thats good - -- not related topic -- Whats the status of gcrypt?. Seems an interesting project. I've always thought frontends to executables are not a clean way to interact with programs. In my opinion, library level is cleaner
>
> Ciao,
Cheers Pedro
>
> Werner
>
>
> [1] A very old version of PGP 2 used to be under the GPL but it used
> to be encumbered by some further restrctions. PGP 2.6 is not available
> under the GPL but under a semi-free license; however due to the
> mandory use of a patented algorithm it is not usefule. PGP 5 and 6
> are proprietary software and 7 is even closed source.
>
Didn't know about that. PGP 7 is closed source?. Wow
> [2] as you probably know, software patents are not only a threat to
> Free Sotware but also the majority of proprietary software vendors.
> See http://www.noepatents.org for further information.
- -- - -----BEGIN PGP PUBLIC KEY BLOCK----- Version: GnuPG v1.0.6 (GNU/Linux) Comment: For info see http://www.gnupg.org mQGiBDqcGZsRBADFIahNPLk8suMlS39m8RqatLgX4dO7PU2F5p1oVvkyB7PaLQCv FREWwfrjGpxAjRnxyZ4TdaFi1oCP495t5R2CdjPZu0EfjsEqosdLXkjDsKl2n4Wo Afb6BaHMJS5PADEI0QfpZOkB8OruAZja/oGmn5rThyjgCxWHUuK1ArmeGwCg7+9a owg9wP1RohePHJSDB9d2HYMD/i7z1X4ev+K90LumgJwSWlScJ7MEip5rw4wqGOkK lF/C2nTYsoX5CVEn/pu7hROL/BWIYtBgkNDaEjsVsyb+4KjQXcZUW5l3ADipWYx2 r9s4sFfeZ9nfhDcG0aNYRcCNkYSZ/WxUkXS8UjVEAEhkFu1BA+6UZmeq3pKtJZTR +HqKA/9zRmgTon36zt2qe9eiR6DyY0EpGEI0iY+KYX6GC/wxizeHBw0FW1eOEoxF GjtxdBv/U9vi7Vgav6aY+pr4la5q6jVabe03Y8yGDFeL8jM+lqww1rzpABiGrF+W qge65zCUjL3jJE5+5yi+KcRyllb1OA7uXQTtsRw+TGq9Dvaaz7QwUGVkcm8gRGlh eiBKaW1lbmV6IChCLk8uRi5ILikgPHBkaWF6ODhAdGVycmEuZXM+iFYEExECABYF AjqcGZsECwoEAwMVAwIDFgIBAheAAAoJEJ7ud33hGMZRj20An2Ce4S/vBTuZDxnL WFBrJRnc3UdaAKDnIPNRbz7r4dh9AuBcpbCE1pQ/SLkBDQQ6nBmqEAQAr7O07Dws 5zAbQvm1hwGthXKCHtIIuWCPdX/XkNG6ZxV/cXgs4LI4oAg3GhttD2JIEk2SoVXE FOf/wIddIDz70/9mIZavMvpR31LxBFSJk0Up3caOvThM90wMttRi7tg7cf04rrMM Phy8T5bOIW/q5SMwZffbJXD7bA0/jDLdQ6MAAwYD/1emSwNTzOOmMCZadoEBpKIE HA35P2/m/SsCI+pQ/OKXKPvvrQKTQqRCcDa5aq31oSiT9M5WQ96BlIGKHRPWGpvm 0822V7M9RF2mYZPIfgKfTSvZpYHzjz+RM7PvBBiBc9l95vy70Sh7SywIF86H80Ag D0dUIDtGlrSANhXjx4EJiEYEGBECAAYFAjqcGaoACgkQnu53feEYxlHdVACgjVhU Y8CKf6MYZgQOR9eIDNvTX0AAn3dwbW1HLxEF5OQKJIsngl0BUlYK =d4S3 - -----END PGP PUBLIC KEY BLOCK----- -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.6 (GNU/Linux) Comment: For info see http://www.gnupg.org iD8DBQE7Lmygnu53feEYxlERAiy9AJ41kddKewcTThyg9jkspIcmrSs7xACgtyYd RjwcuClRjTBONHeCUEi9AjQ= =srg5 -----END PGP SIGNATURE-----