News for hackers. Stuff that matters.
Re:Chrome: From NSS to OpenSSL by fabian2k on Thursday April 10, 2014 @01:16PM (#7568016)
I found the following part in the cons to NSS amusing, or maybe rather frightening:

> Certificate path building is C code designed to emulate Java code, through indirection of an average of 7 layers of macros, two platform abstraction layers, and then the remaining NSS abstraction layers (listed above)

Re:Chrome: From NSS to OpenSSL by joshmoz on Thursday April 10, 2014 @01:33PM (#7568161)
IIRC... That is in reference to libpkix, the certificate validation component of NSS. I believe Mozilla developers are working on a replacement for it, called mozilla::pkix, in large part due to libpkix being overly complex. Last time I checked mozilla::pkix was pretty far along.

https://bugzilla.mozilla.org/show_bug.cgi?id=915930

Re:Chrome: From NSS to OpenSSL by handsomeransoms on Thursday April 10, 2014 @04:22PM (#7569447)
It landed on Nightly a week ago, check it out! You can help us by testing it [0] or reviewing the code [1].

[0] https://wiki.mozilla.org/SecurityEngineering/mozpkix-testing... [1] https://wiki.mozilla.org/SecurityEngineering/mozpkix-testing...

Re:Chrome: From NSS to OpenSSL by cvc on Thursday April 10, 2014 @04:28PM (#7569473)
To be even more precise, this new certificate validation library is the current default in nightly (ff-31), testing is welcome.
Re:Chrome: From NSS to OpenSSL by kaiengert on Thursday April 10, 2014 @01:39PM (#7568219)
Note that NSS contains a classic certificate verification engine, which was originally written in C.

The above statement refers to an external contribution that was added to NSS. It added a second validation engine to NSS, libpkix.

It's true that the libpkix portion is very complicated code, but the above statement doesn't apply to NSS in general.