PingFS

Reminds me of the IPv6 &quot;Type 0&quot; 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:&#x2F;&#x2F;www.secdev.org&#x2F;conf&#x2F;IPv6_RH_security-csw07.pdf</a>

So I take it this is the modern-day equivalent of the mercury delay line?

This idea has been around for a long time; see e.g. Zalewski&#x27;s paper from 2003: <a href="http://lcamtuf.coredump.cx/juggling_with_packets.txt" rel="nofollow">http:&#x2F;&#x2F;lcamtuf.coredump.cx&#x2F;juggling_with_packets.txt</a><p>Cool to see an implementation though!

Heh - the logical abstraction&#x2F;refactoring of &quot;Only wimps use tape backup: real men just upload their important stuff on ftp, and let the rest of the world mirror it&quot;

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.

How much data could you store if you pinged the voyager 2 probe?

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:&#x2F;&#x2F;www.slideshare.net&#x2F;tenderlove&#x2F;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&amp;cd=1&amp;hl=en&amp;ct=clnk&amp;lr=lang_nl%7Clang_en" rel="nofollow">http:&#x2F;&#x2F;webcache.googleusercontent.com&#x2F;search?q=cache:786NsZY...</a>

&gt; PingFS is a set of python scripts ... &gt; 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?

What exactly does this do?