Live data from Hacker News

OpenSSL Audit

cryptoservices.github.io

1–10 of 82 posts

Re: OpenSSL Audit

#4

Key point: "we expect the preliminary results to start coming out towards the beginning of the Summer after we coordinate with the OpenSSL team."

If they're waiting until the summer to publish the preliminary results, this means they probably found some exploitable bugs.

This is an exciting development.

Re: OpenSSL Audit

#5

Key point: "we expect the preliminary results to start coming out towards the beginning of the Summer after we coordinate with the OpenSSL team."

Hopefully this translates to fixing OpenSSL before disclosing the bug(s)

Re: OpenSSL Audit

#6
It's a very sad thing that the world depends on a library that has been virtually unmaintained for years.

Re: OpenSSL Audit

#8
Speaking of OpenSSL, what state are the competing libraries in at the moment? I'd love a version of OpenSSL without all the potentially-insecure legacy code given all the problems its had.

Are there decent implementations of OpenSSL in more secure languages like Rust?

Re: OpenSSL Audit

#10
post #8

Speaking of OpenSSL, what state are the competing libraries in at the moment? I'd love a version of OpenSSL without all the potentially-insecure legacy code given all the problems its had. Are there decent implementations of OpenSSL in more secure languages like Rust?

F# has a proven implementation, but I doubt that's what you're after. OCaml is also getting one for Mirage, but I don't know its status, and it won't be proven correct.
Post reply on HN