Re: [Bug-wget] let's fix the openssl backend once and for all

[Giuseppe Scrivano]

Mike Frysinger <address@hidden> writes:

> On 30 Oct 2014 12:18, Giuseppe Scrivano wrote:
>> Tim Rühsen <address@hidden> writes:
>> > as I wrote to Mike: It is the OpenSSL code within Wget. Wget compiled with 
>> > GnuTLS does not show any problems.
>> 
>> and this remembers us that maintaining two different backends is not a
>> good idea.  I am for just moving to GNU TLS and forget about OpenSSL.
>> It is a bit drastic but I think it is a better move for the long term.
>> And we get rid of the copyright exception as well...
>
> fwiw, in Chromium OS, we've been moving the opposite direction -- away from 
> gnutls & nss and only to openssl.  but i guess it's not that big of a deal to 
> also move to curl and away from wget if need be.  i think most distros tend 
> to 
> default to wget && openssl too (since more projects support openssl).  but 
> having GNU projects favor their own is not surprising.

except that GnuTLS is not a GNU project anymore, so that is not the
reason of my idea; rather the fact of having a compatible license and
just one way of doing the same thing.  They are both used in very
important projects, so I would say they are both very mature and
stable.
So, is there anything that OpenSSL is doing better than GnuTLS and that
has any advantage for wget and its users?

Thanks,
Giuseppe