News for hackers. Stuff that matters.
Re:Vulnerability in Microsoft TLS library could allow remote... by tptacek on Tuesday November 11, 2014 @05:44PM (#8592757)
The issue isn't that native code has special features that mitigate timing attacks. It's that you can look at native code and predict its side effects more easily than you can with high-level code.

Another important difference between native code and high-level code is that timing leaks in high-level code tend to be larger. For instance, it's very difficult to exploit a memcmp timing leak in practice. But Java's string comparison, depending on your JVM, is exploitable over the Internet.

For what it's worth: I wouldn't select C over Java simply to avoid timing attacks. Side channels in JVM code are a legit concern, but not a dispositive one.

[dead]
Re:Vulnerability in Microsoft TLS library could allow remote... by richm44 on Tuesday November 11, 2014 @06:10PM (#8592923)
If you're just talking about me then fair enough - the problems I've publicly identified in TLS are pretty much edge cases. Thomas on the other hand has a pretty good track record if you'd care to check.