[144750] in cryptography@c2.net mail archive

home help back first fref pref prev next nref lref last post

Re: [tahoe-dev] Tahoe-LAFS key management, part 2: Tahoe-LAFS is like encrypted git

daemon@ATHENA.MIT.EDU (Perry E. Metzger)
Wed Aug 19 17:00:26 2009

From: "Perry E. Metzger" <perry@piermont.com>
To: Zooko Wilcox-O'Hearn <zooko@zooko.com>
Cc: tahoe-dev@allmydata.org,  Cryptography List <cryptography@metzdowd.com>
Date: Wed, 19 Aug 2009 15:56:18 -0400
In-Reply-To: <CECF4216-7E4C-4BFE-8D2C-C5388756E10B@zooko.com> (Zooko
	Wilcox-O'Hearn's message of "Wed, 19 Aug 2009 10:11:31 -0600")


Zooko Wilcox-O'Hearn <zooko@zooko.com> writes:
> On Wednesday,2009-08-19, at 10:05 , Jack Lloyd wrote:
>
>> On Wed, Aug 19, 2009 at 09:28:45AM -0600, Zooko Wilcox-O'Hearn wrote:
>>
>>> [*] Linus Torvalds got the idea of a Cryptographic Hash Function
>>> Directed Acyclic Graph structure from an earlier distributed
>>> revision control tool named Monotone.
>>
>> OT trivia: The idea actually predates either monotone or git; opencm
>> (http://opencm.org/docs.html) was using a similiar technique  for
>> VCS access control a year or two prior to monotone's first  release.
>
> Note that I didn't say Monotone invented it.  :-)  Graydon Hoare of
> Monotone got the idea from a friend of his who, as far as we know,
> came up with it independently.  I personally got it from Eric Hughes
> who came up with it independently.  I think OpenCM got it from the
> Xanadu project who came up with it independently.  :-)

The whole thing simply seems like a very obvious use of Merkle hash
trees. It is very understandable that many people familiar with Merkle
trees and related structures would think to apply them this way, since
it is more or less the purpose for which they were intended.

Perry

---------------------------------------------------------------------
The Cryptography Mailing List
Unsubscribe by sending "unsubscribe cryptography" to majordomo@metzdowd.com

home help back first fref pref prev next nref lref last post