bug-wget
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

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


From: Giuseppe Scrivano
Subject: Re: [Bug-wget] let's fix the openssl backend once and for all
Date: Thu, 30 Oct 2014 17:23:06 +0100
User-agent: Gnus/5.13 (Gnus v5.13) Emacs/24.3 (gnu/linux)

Tim Ruehsen <address@hidden> writes:

> On Thursday 30 October 2014 12:18:49 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...
>> 
>> What you all think?
>
> The copyright exception is a non-technical point.
> The opinion of Richard and other GNU project people would be interesting.
> We have GnuTLS and it seems to be pretty good working, much better than two 
> years ago. And the maintainers/developers are very active.

sure, but it was one of the reasons why we wanted to have the GnuTLS
implementation too.  In the meanwhile the GnuTLS developers decided to
detach from GNU, but still the license will allow us to drop the license
exception.
Automatic tests will surely help, but I am in favour of simplification
when it is possible, especially when it comes to drop features we
enable/disable at compile time.  I still don't see enough advantages in
having two different backends that do the same thing, is there any
beside the "we used to use OpenSSL before so it should be more mature
than the other one" ?

Thanks,
Giuseppe



reply via email to

[Prev in Thread] Current Thread [Next in Thread]