4 ms·

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 everyw

by hannob 11y ago

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).

tptacek 11y ago
I stand corrected! Sorry about that.
ancarda 11y ago
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?
- hannob 11y ago
  The bug was introduced with an assembly optimization that got added to OpenSSL after LibreSSL forked the codebase.
- deleted 11y ago
  [deleted]
- masklinn 11y ago
  > 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.