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 (was: Patc


From: Tim Ruehsen
Subject: Re: [Bug-wget] let's fix the openssl backend once and for all (was: Patch Test-proxied-https-auth.px)
Date: Thu, 30 Oct 2014 16:57:45 +0100
User-agent: KMail/4.14.2 (Linux/3.16-3-amd64; KDE/4.14.2; x86_64; ; )

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.

It should be possible to fix Wget's OpenSSL usage. And that should be it.
Right now I can't say for sure if that problem (Test-proxied-https-auth.px 
failure with Wget+OpenSSL and valgrind) doesn't come from valgrind itself.
I need some more time to investigate (or someone else can help, who better 
understand OpenSSL).

Once fixed, not much time would go into the OpenSSL code...
... as long as we set up automated tests. Darshit already mentioned in his 
post from 20.10.14 (Summary of Pending Patches) to set up a Travis-CI test on 
a regular basis. Testing both GnuTLS and OpenSSL backends would be easy going.
Such a setup would also allow for e.g. automated testing of different locales 
(known bug: Wget heavily fails with turkish locales).

Tim

Attachment: signature.asc
Description: This is a digitally signed message part.


reply via email to

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