[liberationtech] Auto expiring document/files & 'rights to be forgotten'
Steve Weis
steveweis at gmail.com
Thu Jan 26 11:39:01 PST 2012
You might be thinking of Vanish by Yoshi Kohno et al.:
http://vanish.cs.washington.edu/
http://www.cs.washington.edu/homes/levy/vanish.pdf
Ed Felten, Alex Halderman, Brent Waters, et al. have a Sybil attack against
it here:
https://jhalderm.com/pub/papers/unvanish-ndss10-web.pdf
Regardless of the attack, Vanish does not prevent local copies of the data.
As people have already pointed out, if you let someone view static content
on their own hardware, they can copy it. You can make it inconvenient and
perhaps lossy, but can't prevent it completely.
On Thu, Jan 26, 2012 at 11:18 AM, Tom Ritter <tom at ritter.vg> wrote:
> There was a technology (that didn't work for realistic threat models)
> that took a document and split among a number of servers. Over time,
> these pieces would decay and be removed until you were no longer able
> to reassemble the document. That sounds similar to what you're after.
>
> It doesn't work for all the reasons already mentioned, but it was a
> concrete open source implementation of an attempt. If only I could
> remember its name...
>
> -tom
> _______________________________________________
> liberationtech mailing list
> liberationtech at lists.stanford.edu
>
> Should you need to change your subscription options, please go to:
>
> https://mailman.stanford.edu/mailman/listinfo/liberationtech
>
> If you would like to receive a daily digest, click "yes" (once you click
> above) next to "would you like to receive list mail batched in a daily
> digest?"
>
> You will need the user name and password you receive from the list
> moderator in monthly reminders.
>
> Should you need immediate assistance, please contact the list moderator.
>
> Please don't forget to follow us on http://twitter.com/#!/Liberationtech
>
More information about the liberationtech
mailing list