News for hackers. Stuff that matters.
Re:How not to sign a JSON object by jcranmer on Wednesday July 24, 2019 @01:59PM (#20517820)
> We do have a blog post from last year that tells you what we think you should do if you want to be safe and you know what kind of abstract thing (e.g. signing, MACing, etc) you need

A little bit off-topic, but what is your opinion on NSS versus OpenSSL? Or LibreSSL and BoringSSL?

Re:How not to sign a JSON object by lvh on Wednesday July 24, 2019 @02:32PM (#20518170)
What do you want to accomplish? Do you want good implementations of cryptographic primitives, or something else?

As a general rule: OpenSSL, BoringSSL if you can get away with it, don't use NSS or LibreSSL. But that presupposes that using a library like OpenSSL was the right answer to begin with :)

Re:How not to sign a JSON object by tptacek on Friday July 26, 2019 @01:48PM (#20536683)
I used to be a proponent of NSS, when people who were much more closely involved with TLS implementations were quite down on it. NSS was the first TLS library I really read "cryptographically" (it hosted the Bleichenbacher e=3 signature verification bug, which made Firefox vulnerable to signature forgery) and I found the code really easy to follow, unlike OpenSSL's. Ultimately, they were right, and I was wrong: in this space, you want a lot of attention and effort on your TLS library, and OpenSSL is the most seriously maintained TLS library. For the same reason: OpenSSL over LibreSSL.