On Monday 23 April 2012 17:06:27 Yang Tse wrote:
> On Mon, Apr 23, 2012 at 2:01 PM, Kamil Dudka <kdudka(a)redhat.com> wrote:
> > You can try to compile libcurl against NSS instead of OpenSSL. NSS uses
> > another approach to prevent this kind of attack and does not send empty
> > packets.
> Honest question...
> Which is current situation regarding libnsspem library availability
> outside of RH universe?
The good news is that the libnsspem library finally has an upstream:
The long term goal is to merge the sources directly to NSS upstream, although
I doubt it will happen anytime soon. We have also fixed a bunch of bugs as
you can see from the Revision Log:
> It seems it is required in order to allow
> usage and interoperability with PEM certificates.
If you need to handle them in the same way as with OpenSSL, it is indeed
required. Another choice is to put the required certificates and keys to
the NSS database. The database can be shared with Firefox, Thunderbird,
and other applications using NSS.