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: Darshit Shah
Subject: Re: [Bug-wget] let's fix the openssl backend once and for all (was: Patch Test-proxied-https-auth.px)
Date: Sat, 1 Nov 2014 06:08:33 +0530
User-agent: Mutt/1.5.23 (2014-03-12)

On 10/30, Daniel Stenberg wrote:
On Thu, 30 Oct 2014, Giuseppe Scrivano wrote:

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...

Allow me to throw a (much more) crazy idea at you:

Consider sharing the TLS backend setup that libcurl has[1]. It currently supports 9 (or 11, depending on how you count libressl/boringssl) TLS libraries using a unified internal function set... It would for example allow more small foot-print libs to be used, and the native TLS libs on platforms like mac and windows.

I was just about to throw the same idea to this list. Well, not exactly the same. I have been pondering about a single internal API for SSL libraries. But since cURL already has them and is willing to share, I don't see why not.

[1] = there would be some amount of work involved to make it happen, from both parties, but I think there would be mutual benefit. The code is somewhat separated in the libcurl code base already, but would need some further polish to get properly useful.

I'd be willing to help in making this possible. I've never really hacked on the libcurl code, but it shouldn't be too hard. Will take a look at it when I can.


--

/ daniel.haxx.se

--- end quoted text ---

--
Thanking You,
Darshit Shah

Attachment: pgpPUxerTINJv.pgp
Description: PGP signature


reply via email to

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