Home
| Calendar
| Mail Lists
| List Archives
| Desktop SIG
| Hardware Hacking SIG
Wiki | Flickr | PicasaWeb | Video | Maps & Directions | Installfests | Keysignings Linux Cafe | Meeting Notes | Linux Links | Bling | About BLU |
You know, this could be really problematic on things like sans and nas storage systems. I mean, unless of course you build them yourself but honestly, could you just imagine the lawsuits if somehow a file was saved on the san but the inode/equivalent was deleted but the file still remained, and retrieved? I mean, is there file destruction software for nas/san stuff? ~Ben On Thu, Apr 17, 2008 at 1:32 PM, Dan Ritter <[hidden email]> wrote: > On Thu, Apr 17, 2008 at 01:28:48PM -0400, Ben Holland wrote: > > So then the program would basically have to keep track of how many times > the > > actual file was stored as well as all locations at all times. Wouldn't > this > > kinda overhead be huge? ~Ben > > If what you want is assurance that the data you stored has by > gosh been erased in every incarnation, then you have to do even > more than that -- you also need to monitor every program that > reads your sensitive information to make sure it doesn't write a > copy elsewhere. You'll probably need to track and scrub your > swapfiles, too. > > Security question number one: what's your threat model? > Question number two: what's it worth to you? > > -dsr- > > -- > http://tao.merseine.nu/~dsr/eula.html<http://tao.merseine.nu/%7Edsr/eula.html>is hereby incorporated by reference. >
BLU is a member of BostonUserGroups | |
We also thank MIT for the use of their facilities. |