4 ms·
Does anyone know how feasible this kind of attack is with real world network latency and server load fluctuations? In the end it comes down to statistics, but i
by phreeza 16y ago
Does anyone know how feasible this kind of attack is with real world network latency and server load fluctuations? In the end it comes down to statistics, but i could imagine forging a token this way might take a very high number of failed attempts, which might then trigger other security mechanisms?
- metachris 16y ago"We have shown that, even though the Internet induces significant timing jitter, we can reliably distinguish remote timing differences as low as 20µs. A LAN environment has lower timing jitter, allowing us to reliably distinguish remote timing differences as small as 100ns (possibly even smaller). These precise timing differences can be distinguished with only hundreds or possibly thousands of measurements." http://www.cs.rice.edu/~dwallach/pub/crosby-timing2009.pdf http://www.cs.rice.edu/~dwallach/pub/crosby-timing2009.pdf Inside Amazon datacenters you also have lan-like performance.
- twp 16y agoFrom my understanding, actually surprisingly so. Stats allow you to cope with latency and uncertainty - just ask the NTP gurus. There's a reference somewhere, but effectively these attacks are possible over surprisingly long distances/dodgy connections.
- SoftwareMaven 16y agoAnd even more so, with people potentially sitting right next to each other on services like AWS, RackSpace, etc.
- NateLawson 16y agoSee "Get off my cloud" for an example how you can exploit the allocation algorithms to intentionally locate yourself on the same machine as your target. http://cseweb.ucsd.edu/~hovav/dist/cloudsec.pdf http://cseweb.ucsd.edu/~hovav/dist/cloudsec.pdf [pdf]