[Pkg-openssl-devel] Bug#501145: Bug#501145: Please clearify license issue openssl vs. gpl

[Bastian Germann]

On Sat, 04 Oct 2008 22:18:51 +0200 Vincent Bernat <bernat at debian.org> wrote:
> OoO Pendant le  journal télévisé du samedi 04  octobre 2008, vers 20:48,
> Christian Engwer <christi at uni-hd.de> disait :
> 
> > To make the situation even more confusing, Debian offers a lot of
> > packages, which are linked against libssl and licensed under GPL (e.g.
> > kcontrol, inkscape, balsa, ...).
> 
> All those packages need the  OpenSSL exception. The other solution is to
> link them against  GNU TLS (which is possible  because they are licensed
> under GPL, as well as the OpenSSL compatibility wrapper).
> 
> We  also have  packages  that  linked against  OpenSSL  and against  GPL
> libraries without OpenSSL exception.  This is not authorized. An example
> is Python which is linked to libssl and to libreadline.
> 
> We have GPL  packages that link against packages  linked to OpenSSL. For
> example, quagga was linked to  libsnmp which is linked to libssl. quagga
> has  handled  this   issue  by  disabling  SNMP  support   (which  is  a
> pity). There are other packages in this case.
> 
> Those licensing  issues are a mess.  I think that the  problem should be
> raised after lenny. Right now, people are focused to lenny. I have tried
> to raise the problem with Python without any success.
> -- 
> I AM SO VERY TIRED
> I AM SO VERY TIRED
> I AM SO VERY TIRED
> -+- Bart Simpson on chalkboard in episode AABF20

I think, this issue can be closed. See the last comments on #924937.
It took a little longer...