Please test :)

Werner Koch wk at gnupg.org
Tue Aug 25 14:45:00 CEST 2009


On Mon, 24 Aug 2009 03:46, dshaw at jabberwocky.com said:

> which is what is linked with the keyserver helpers.  My notes say we
> split libcompat and libutil in 2006 for licensing reasons, as the
> keyserver helpers might be linked with OpenSSL, which is not GPL

Right, I forgot about this.  

> Now, it would be possible to move the tilde expanding code to
> libcompat (or even just implement things slightly differently), but I

Yeah we should do that:  Add the exception to gnupg14/util/fileutil.c
and make sure that it does not need other stuff from util/ .

BTW, srv.c, which is used in libcompat, is also missing the OpenSSL
exception.  Easy to fix.

> notice that GnuPG 2.x doesn't do any of this stuff with a different
> library, and just uses libcommon everywhere, including in the
> keyserver helpers.

Right. 

Actually, I forgot about this problem while porting the keyserver code
to GnuPG-2, or assumed that OpenSSL is not used.  Those who distribute
GnuPG-2, need to take care of the license, meaning to use gnutls, yaSSL
or another GPL compatible SSL library.  In particular gnutls is a good
choice because gnutls uses libgcrypt which is a requirement for GnupG
anyway.

> Is libcompat really necessary for GPL compliance?  If not, this is an
> easier problem.  If it is necessary, we need to fix GnuPG 2.x.

We should allow the (indirect) use of OpenSSL with GnuPG 1.4, thus we
need to extend libcompat.  No need to care about it for GnuPG-2.

Shall I take care of the tilde code?


Shalom-Salam,

   Werner


-- 
Die Gedanken sind frei.  Auschnahme regelt ein Bundeschgesetz.




More information about the Gnupg-devel mailing list