[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]
Re: Regarding summer of code 2008(writing device drivers)
>> Also, the technique seems susceptible to data injection. What do
>> you think?
> I don't see why there's any more chance of it with this scheme than
> with normal TCP.
Sleeper injections, perhaps? With normal TCP, if you inject a packet,
it has to be in-window, or it's dropped. With this, you can inject a
packet and have it sit in a cache for a more or less unlimited time and
then have it crawl out and damage the data stream. (Nontrivial, but
I'd be very reluctant to declare it impossible. A lot of traffic is a
lot more predictable in practice than it's promised to be by theory.)
> First, how much data can be cached in RAM on the receiving machine?
Quite a lot, if it wants to. I'm regularly seeing machines these days
with more RAM than some of my machines have _disk_.
/~\ The ASCII der Mouse
\ / Ribbon Campaign
X Against HTML mouse%rodents.montreal.qc.ca@localhost
/ \ Email! 7D C8 61 52 5D E7 2D 39 4E F1 31 3E E8 B3 27 4B
Main Index |
Thread Index |