4 ms·
Explain please. This is about direct device io exposing memory remotely through timing attacks. Ssh info is just one example of what can be leaked.
by cma 7y ago
Explain please. This is about direct device io exposing memory remotely through timing attacks. Ssh info is just one example of what can be leaked.
- dooglius 7y agoMemory isn't being exposed, just the fact that something is touching memory in a certain place. That ssh login keystrokes leak via side channels is a long standing flaw in ssh. Memory access patterns can already be inferred from network response latency on any processor, nothing about that is new or surprising.
- cma 7y agoThis doesn't give more timing precision than previous techniques?
- angry_octet 7y agoIt is a super accurate way of timing packet receipt. For keystrokes sent across a WAN that wouldn't normally help you. But this really isn't about ssh, which is just used as a cute demo of the power of traffic analysis and side channels; this is about remote access to local side channels in the memory system.