Re:X86 is a high-level language
by JonnieCache on Wednesday March 25, 2015 @02:07PM
(#9264760)
The solution i've seen is:
this assumes that the attacker cannot control any non-relevant part of request_content.
[ Parent
| on HN ]
Re:X86 is a high-level language
by matthewmacleod on Wednesday March 25, 2015 @07:54PM
(#9266882)
As far as I can tell, that would not be secure – wouldn't it end up being essentially cryptographically secure random timing noise? We already know that random jitter doesn't work, because it can be averaged out given enough samples.
I'm not a cryptography guy though, so I could well be wrong!
Re:X86 is a high-level language
by TheLoneWolfling on Thursday March 26, 2015 @12:08AM
(#9267770)
It cannot be averaged out, as there is no way to take multiple samples.
Look at it: for any specific input it always sleeps for a deterministic amount of time. Unlike random timing noise, which can be averaged away.
You take averages and all you know is the value of (actual time + some unknown value) very precisely. That doesn't help you.
(He is, however, missing that it should also have a random salt, generated once and stored.)
Of course, this is still breakable most of the time.
This seems like it's insecure if the attacker can predict request_content, too.
Re:X86 is a high-level language
by TheLoneWolfling on Wednesday March 25, 2015 @04:14PM
(#9265615)
That's secure as long as the hash is (securely) salted.