Better proxy support available via libcurl?

Alphax alphasigmax at
Fri Aug 4 01:27:03 CEST 2006

David Shaw wrote:
> Like I said, I'm perfectly okay doing nothing, but now that the issue
> has been raised, it is difficult to just drop, as we have a problem
> today that needs an answer: it has been asserted that distributing
> binaries of GnuPG that link to libcurl built on OpenSSL violates the
> GPL.  That is to say, it is *against the law* to do so, and the
> copyright holder of GnuPG (FSF) could, if they chose to, take the
> infringer to court.
> It is not right to make such a statement and then walk away.  All that
> accomplishes is to create FUD, and if a packager decides to throw up
> their hands and not package GnuPG rather then get involved in these
> questions, then we have caused harm.

How hard is it to determine if libcurl has been built against OpenSSL or
not? One possible solution would be to detect if it had been during the
autoconf/automake process and not link to libcurl if it was (overridable
somehow?); if it was, /then/ start printing big warnings.

> I think we need an official answer yes or no whether this is legal as
> things are now.  It is difficult to design for the future if we do not
> know where we stand today.

Has anyone asked on debian-legal or similar?

        Death to all fanatics!
  Down with categorical imperative!
OpenPGP key:

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 569 bytes
Desc: OpenPGP digital signature
Url : /pipermail/attachments/20060804/49e2d70d/signature.pgp

More information about the Gnupg-devel mailing list