News for hackers. Stuff that matters.
Re:Chrome: From NSS to OpenSSL by majke on Thursday April 10, 2014 @12:38PM (#7567657)
And here is compulsory email thread explaining some context:

https://groups.google.com/forum/?_escaped_fragment_=msg/mozi...

> Strange that "PKCS#11 support" is listed as a "con" for NSS

> It was not accidental that it was listed under "Con", nor do I see ENGINE_pkcs11 as a "Pro"

Re:Chrome: From NSS to OpenSSL by ewindisch on Thursday April 10, 2014 @01:12PM (#7567977)
This conversation circles back to Theo de Raadt's argument that developers are caring too much about performance in security-critical applications.
Re:Chrome: From NSS to OpenSSL by pfortuny on Thursday April 10, 2014 @01:43PM (#7568257)
Which is the typical point in which Theo de Raadt is right even though he may be saying so quite singularly.

This is another instance of the lack of 'engineering' in Computer Science/Programming/you name it. Engineers have long ago learnt that you need "automatic" standards and compliance before, during and after building anything, and that the best practice is always assuming thing will go wrong.

This, unfortunately, is not the case with programming as we can see time and again.

But I digress.

Re:Chrome: From NSS to OpenSSL by mike_hearn on Thursday April 10, 2014 @03:43PM (#7569176)
Smartcard support is pretty important for a lot of people. If Chrome drops that feature, that would be a huge shame.
Re:Chrome: From NSS to OpenSSL by nvdk on Friday April 11, 2014 @02:04AM (#7571433)
every belgian citizen is issued a pkcs e-id, not supporting it means they all need another browser to do their taxes and log in to healthcare websites...