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

[Giuseppe Scrivano]

Darshit Shah <address@hidden> writes:

> On Thu, Oct 30, 2014 at 4:48 PM, Giuseppe Scrivano <address@hidden> 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...
>>
>> What you all think?
>
> I think OpenSSL is being used by way too many of our users as a SSL
> backend and that we should continue to support it. Despite what the
> project aimed for, GNUTLS has not managed to gain the adoption /
> popularity that OpenSSL enjoys. In my opinion, we should clean up our
> code-base and ensure that everything works with a good set of unit
> tests.
>
> Maintaining two backends for OpenSSL and GNUTLS may be difficult, but
> it is something we must work with. More people use Wget with the
> OpenSSL backend than the number of people who use Wget on WIndows +
> VMS. Yet we continue to support those architectures and want to
> eliminate OpenSSL? Yes, it's hard, but we only need to up the ante and
> clean up the code base, not run away from the real problem and simply
> drop OpenSSL.

yes, but in the OpenSSL vs GnuTLS case they have only to change a
library and they will have the same functionalities, while dropping
support for Windows or VMS means not offering any alternative to these
users.

What do you think about the idea Daniel proposed on this same thread?

Giuseppe