Re: legal implications of linking to libssl/openssl

2018-05-06 Thread Francesco Poli
On Sun, 06 May 2018 04:08:26 + Sandro Tosi wrote: > > The situation is currently unchanged, the OpenSSL license is > > incompatible with the GNU GPL family of licenses and an exception is > > needed to allow combining code under those licenses and OpenSSL in the > > same work. > > >

Re: legal implications of linking to libssl/openssl

2018-05-05 Thread Sandro Tosi
> The situation is currently unchanged, the OpenSSL license is > incompatible with the GNU GPL family of licenses and an exception is > needed to allow combining code under those licenses and OpenSSL in the > same work. > https://people.gnome.org/~markmc/openssl-and-the-gpl.html thanks Paul,

Re: legal implications of linking to libssl/openssl

2018-05-05 Thread Paul Wise
On Sun, May 6, 2018 at 8:39 AM, Sandro Tosi wrote: > I know there were issues linking with openssl, but i dont know if it's > still accurate, so i would like to ask the list: is it ok from a legal pov > to switch from gnutls to openssl for transmission? The situation is currently unchanged, the

legal implications of linking to libssl/openssl

2018-05-05 Thread Sandro Tosi
Hello, in transmission we received a bug[1] about excessive memory usage with our current library (libcurl3-gnutls) which is reported fixed[2] by replacing it with its openssl counterpart (libcurl4-openssl). I know there were issues linking with openssl, but i dont know if it's still accurate, so