PingFS
shysecurity.com
PingFS
1–10 of 17 posts
Re: PingFS
#2Heh - 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"
Re: PingFS
#3Reminds me of the IPv6 "Type 0" routing header disaster, where you could store data in routing loops.
See, e.g. slide 30 of: http://www.secdev.org/conf/IPv6_RH_security-csw07.pdf
Re: PingFS
#4So I take it this is the modern-day equivalent of the mercury delay line?
Re: PingFS
#5Would it be considered bad form to attach this application to a RFC 1149 network? It might actually increase the recoverability of the data in question.
Re: PingFS
#6What exactly does this do?
Re: PingFS
#7What exactly does this do?
My understanding is this:
It's a filesystem that stores it's data in a temporary packet. So when you ping a server to see if it's up, it sends back the data you sent so you can verify it's okay. It's implemented as a filesystem using FUSE (which allows for all kinds of user space filesystems) so the OS just uses it like a disk or network storage and so on. I believe it works by spamming out pings with the data in them, and when they come back just send them out again.
Re: PingFS
#8What exactly does this do?
seems like it essentially keeps data stored by catching data from ICMP (ping) packets, rewrapping them in another ping packet and shoving them back on the network.
Think of it kind of like network RAM, the data isn't stored anywhere persay and if either host fails to bounce back the payload the data is lost since it wasn't stored on any single machine and only kept alive in limbo.
Re: PingFS
#9What exactly does this do?
As oakwhiz pointed out, this is conceptually similar to delay-line memory [1]. At least it doesn't require 100○ F mercury.
Re: PingFS
#10How much data could you store if you pinged the voyager 2 probe?