5 ms·
I'm super confused by the statement "The unix time component has a more broad domain, but this turns out to be not a practical problem (see later)." I don't kn
by addingnumbers 5y ago
I'm super confused by the statement "The unix time component has a more broad domain, but this turns out to be not a practical problem (see later)."
I don't know what exactly he expected us to "see later," except that he knows exactly when the target machine rebooted down to a 15 second window because he already had full control over it before starting the attack...
- londons_explore 5y agoI can imagine cases where an attacker could have good knowledge of the reboot time of a system. For example, they could ping it for months waiting for a maintenance reboot. Or they could flood the machine with requests, hoping to cause some monitoring system or human to reboot it. But overall, it seems unlikely...
- Arnavion 5y ago>I don't know what exactly he expected us to "see later," See all mentions of "Attack #2"
- addingnumbers 5y agoThis only makes it more confusing: > a day of unixtime + potential pids makes ~86420 potential XIDs, this is a feasible attack vector. The number of potential XIDs isn't timestamp PLUS pid, it's timestamp TIMES pid, right? Totaling not "~86420" but 2,160,000, right? But where does he get "a day" from? How does he know the target wasn't booted yesterday, or a month ago?