Slashdot Mirror
Packet Juggling - Floating Data Storage
Filthmaster writes "I just saw an interesting paper that has been posted to bugtraq, full-disclosure and vulnwatch. It deals with the principles of stealthily using network infrastructure as either short-term or long-term storage. Not sure if I'm ready to implement it, but it makes interesting food for thought." There's also a mirror up.
If it were quick enough and timed well enough, could network bounced packets be enough for some really quick swapped out swap space? gig ethernet gets around 1ms to my next machine, and thats 10 times quicker than my hard drive (10ms access time) so if I could store swap in that space, would that work?
I was thinking of tunneling ssh over sms before this, but that sounds just silly now.
... in which complete computer memories worked like this: those were called mercury delay line memories, in which pressure waves in mercury lines basically held information.
The UNIVAC I had such an 18-channel memory. More information can be found here, here, and here.
These channels could hold a whopping kilobit!
Support a Europe-related section on Slashdot!
When I was in college back in the Good Old Days (tm) of the Internet, I had a friend who sometimes stored files "in transit", so to speak, by emailing them to himself with explicit routing in the To address. He would send the message on a long circuit of several machines around the country and he had a script to automatically reforward them once they got back if he didn't save them within a certain period of time. Back in the day you could do this by setting the To address to something like "@hostone.com,@hosttwo.com,me@myhost.com" (see RFC 821 sec 3.6) and since the network and the machines on it were much slower in those days, if you added enough hosts then you could introduce a significant delay and have lots of files stored in transit (actually, on the various mail servers) even though your own disk quota was nearly used.
Explicit routing is long gone, but it is an interesting early manifestation of the same principle: the network is my hard drive.
I remember that when I was at the University, I explained to someone that with satellites at 37000 km from us, information took a quarter of a second to go there and back to earth. So if you use a 500 Mbps link, you can store 15 MBytes of data in the distance between, on an absolutely zero cost medium, during 0.25 second. And if you were confident enough in the reliability, you could even put a bouncer on earth, which goal would only be to resend the stream to the satellite and keep it looping. You would have 15 Mbytes of free storage with an average access time of 125ms (250ms max). Although absolutely useless, that would be as fun as TCP/IP over pigeon routing :-)
Willy
I will never put a sig.