2 ms·
This is the only point where I wish the paper was more clear... "Similar to Section 5.1, we wrote a custom SSH client that launches our spy program, the spy pr
by zaroth 10y ago
This is the only point where I wish the paper was more clear...
"Similar to Section 5.1, we wrote a custom SSH client that launches our spy program, the spy program collects the timing signals during the handshake. At the same time it performs an SSH handshake where the protocol messages and the digital signature are collected for our attack."
I think that 'spy process' must be local to observe the low-level cache timings they are using to perform the attack, but I haven't found anywhere they come out and say that explicitly.
- joeyrideout 10y agoExactly. The paper is frustratingly unclear on what the exploit scenario is. "...we wrote a custom SSH client that launches our spy program, the spy program collects the timing signals during the handshake..." I have a bad feeling that this means an attacker with a custom client can extract private key information over the network by repeatedly establishing connections with a vulnerable server.
- tptacek 10y agoI believe they're talking about a test harness they built, to synchronize collection of cache traces with the execution of the handshake. FLUSH+RELOAD requires a co-resident attacker (they need to be on the same hardware, though not necessarily the same VM).