Keys are generally more sensitive than data; but yes, it should all be kept secure. I've been asking compiler authors for 13 years to give us better tools, e.g. to mark variables as "cannot be used in control flow or address computation". Alas, no progress yet...
-
-
Maybe Amazon can find some smart compiler people and get them to do this? It would help everybody's security. ;-)
1 reply 0 retweets 0 likes -
Replying to @BRIAN_____ @cperciva
LuckyMinus20 changed my mind on that. The branch free code fixes for Lucky13 went through a lot of review, loads of eyes, and patched a vulnerability. But then it unintentionally regressed within 18 months.
0 replies 0 retweets 0 likes -
Replying to @BRIAN_____ @cperciva
The LuckyMinus20 was a logic error, and worse than the Lucky13 side-channel (IMO), at least for TLS (not DTLS). That's what I mean when I say it's too hard to write this kind of code without risking worse problems.
1 reply 0 retweets 1 like -
http://www0.cs.ucl.ac.uk/staff/b.cook/VSSTE18_sidetrail.pdf … can catch the LuckyMinus20 regression, we actually used it as a target case. It needs more than the secret modifier, it also needs to know the entry and exit points, but since the logic error is data-dependent, it can catch it too.
0 replies 0 retweets 1 like
We're about to take CBC out of s2n's default set, it's finally, finally, small enough a percentage of traffic to be viable. Curiously RC4 and 3DES each went much faster.
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.