Hacker News Reader

Not really surprising. This is a common bug, and people are looking for it much more aggressively over the last year. Even Nacl had one of these bugs!

There was a carry propagation bug in OpenSSL/BoringSSL/LibreSSL just a few weeks ago.

View on HN

The surprising thing is not the bug, it's that go didn't verify the result of the CRT calculation. That's a standard countermeasure (although not present everywhere, Florian Weimer recently did some work on patching implementations that were lacking this check).

And nit: The OpenSSL bug didn't affect libressl (I discovered it, I checked for that).

I stand corrected! Sorry about that.

How do bugs that affect OpenSSL not affect LibreSSL? Surely any bugs that were fixed in LibreSSL would have been shared with OpenSSL, right? Or is it legacy code that was removed during the Valhalla cleanup?

The bug was introduced with an assembly optimization that got added to OpenSSL after LibreSSL forked the codebase.

> Surely any bugs that were fixed in LibreSSL would have been shared with OpenSSL, right? Or is it legacy code that was removed during the Valhalla cleanup?

hannob gave the reason, but bug could also be unwittingly removed by separate cleanup e.g. generic replacement of unsafe functions/practices by safer ones.

Are you rerferring to CVE-2015-3193? I believe it did not affect libressl

Reply on news.ycombinator.com