Reminds me of the IPv6 "Type 0" routing header disaster, where you could store data in routing loops.<p>See, e.g. slide 30 of: <a href="http://www.secdev.org/conf/IPv6_RH_security-csw07.pdf" rel="nofollow">http://www.secdev.org/conf/IPv6_RH_security-csw07.pdf</a>
This idea has been around for a long time; see e.g. Zalewski's paper from 2003: <a href="http://lcamtuf.coredump.cx/juggling_with_packets.txt" rel="nofollow">http://lcamtuf.coredump.cx/juggling_with_packets.txt</a><p>Cool to see an implementation though!
Heh - the logical abstraction/refactoring of "Only wimps use tape backup: real men just upload their important stuff on ftp, and let the rest of the world mirror it"
Would it be considered bad form to attach this application to a RFC 1149 network? It might actually <i>increase</i> the recoverability of the data in question.
By the way, the linked slideshow is hilarious, never seen it before:
<a href="http://www.slideshare.net/tenderlove/worst-ideas-ever" rel="nofollow">http://www.slideshare.net/tenderlove/worst-ideas-ever</a>
Link to Google Cache because the server seems to be overloaded:<p><a href="http://webcache.googleusercontent.com/search?q=cache:786NsZY7idIJ:www.shysecurity.com/posts/pingfs+http://www.shysecurity.com/posts/pingfs&cd=1&hl=en&ct=clnk&lr=lang_nl%7Clang_en" rel="nofollow">http://webcache.googleusercontent.com/search?q=cache:786NsZY...</a>
> PingFS is a set of python scripts ...
> Each file ... sent over the wire in an ICMP echo request, and promptly erased from memory.<p>can you actually reliably erase anything from memory in python?