Re: [PATCH 1/3] nss: use a better API for controlling SSL version
Date: Mon, 2 Dec 2013 14:19:26 +0100
On Friday 29 November 2013 16:33:03 Daniel Stenberg wrote:
> On Fri, 29 Nov 2013, Kamil Dudka wrote:
> > On the other hand, I am not aware of any secured NSS release older than
> > 3.14. Upstream does not backport security fixes to older releases and
> > neither does Red Hat. Even the oldest supported RHEL now uses NSS 3.14:
> > Hence I propose to just update docs/INTERNALS to require the new version
> > and to check for the new symbols in the autoconf check enabling the build
> > against NSS. Any objections?
> Not really other than that 3.14 seems awfully young by libcurl standards as
> the oldest version of a 3rd party to support, but I also think that if
> there's nobody around that needs support for older stuff it feels
> unnecessary to bend over backwards to support that.
> If someone else comes along later and absolutely needs support for older
> NSS I guess the work load is then rather shifted to that person/company.
> So, no objections from me!
Thanks for the confirmation! The amended version of [PATCH 1/3] is attached.
Should I postpone pushing this patchset until 7.34.0 is out?
- text/x-patch attachment: 0001-nss-use-a-better-API-for-controlling-SSL-version.patch