[tahoe-dev] Noobie asks how does Tahoe differ from MS Live Mesh?

Andrej Falout andrej at falout.org
Fri Aug 7 00:23:20 UTC 2009

So I guess the only thing Orwell did not predict was OpenSource...

Oh how very happy that makes me feel :-)

Andrej Falout

On Fri, Aug 7, 2009 at 2:39 AM, Zooko Wilcox-O'Hearn <zooko at zooko.com>wrote:

> On Thursday,2009-08-06, at 10:06 , CyberAxe-Hotmail wrote:
> > How does Tahoe differ from Live Mesh
> Here's an old blog entry of mine from when I presented Tahoe-LAFS at
> a workshop attached to the Association for Computing Machinery's
> Conference on Computer and Communications Security.
> http://zooko.com/log-2008.html#d2008-11-13-ACM_CCS_notes
> My presentation on Tahoe went well. At the end a fellow named Zhuowei
> Li, who works on Microsoft Azure, raised his hand to ask a question.
> It was a bit difficult for me to understand him, as English isn't his
> first language. "How do you keep track of all the users's files, to
> see if they have some bad files like pornography or something in case
> the police ask for it?".
> "Well, uh..." I hesitated for a second, "in general, we don't. Many
> of our users do ask us to keep a copy of their root cap so that we
> can give it back to them if they forget their password. If we have
> their root cap, then in theory we can traverse all their files and
> inspect them, but we have a policy of not looking at users' files,
> and if they didn't share their root cap with us in the first place
> then there is no way for us to see their files even if we wanted to."
> "But you have to!", he exclaimed.
> "What? Why?"
> "Legal tells me that we have to keep a catalog of files such as
> pornography so for example if the FBI comes."
> "Ah," I said, "Well, I believe that the Microsoft legal department
> told you that, but if so then that is a Microsoft policy, not a law
> in the United States. There's no requirement for my company to have
> the same policy."
> Later I spoke to him in person, and added that if Microsoft wanted to
> buy http://allmydata.com and use Tahoe in Azure, they could easily
> implement that policy just by making sure they had copies of all the
> customer's read-caps.
> _______________________________________________
> tahoe-dev mailing list
> tahoe-dev at allmydata.org
> http://allmydata.org/cgi-bin/mailman/listinfo/tahoe-dev
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://tahoe-lafs.org/pipermail/tahoe-dev/attachments/20090807/3ba9f384/attachment.html>

More information about the tahoe-dev mailing list