Better proxy support available via libcurl?

David Shaw dshaw at
Wed Aug 2 14:17:32 CEST 2006

On Wed, Aug 02, 2006 at 08:47:13AM +0200, Werner Koch wrote:
> On Wed,  2 Aug 2006 02:36, David Shaw said:
> > I'm not sure I understand.  Check if cURL is linked to OpenSSL?  What
> > would we do differently if it was?
> In that case we can't use cURL  at least a fat warning should be
> displayed.

I must disagree.  Unless I am seriously misreading the GPL, the
restriction would be on *distributing* a binary with GPG linked to an
OpenSSL libcurl, and even then the restriction depends on whether
OpenSSL is considered part of the OS or not.

Such a question (whether OpenSSL is part of the OS) should be up to
the packager of the binary and the maker of the OS.  Debian seems to
have decided that OpenSSL is not part of the OS, while Fedora and Mac
OSX decided it that it was.  Either way the OS goes, it's not
something we can reasonably answer within GPG.

The packager of the binary has many choices: they can build with
OpenSSL+libcurl, they can build with GnuTLS+libcurl, they can build
with plain libcurl, or they can build without libcurl at all.  We've
given them all the tools they need to make GPL-compliant packages.
It's up to them to decide what their platform requires.

I'd be happy to write a paragraph or two for the README file about
this.  It's not even a libcurl-specific issue: the LDAP keyserver
helper can link to OpenLDAP, which can also be built with OpenSSL.


More information about the Gnupg-devel mailing list