From: Tom Lord <lord@emf.net>
To: cscott@cscott.net
Cc: git@vger.kernel.org, robj@unrealities.com
Subject: Re: Val Henson's critique of hash-based content storage systems
Date: Fri, 29 Apr 2005 13:37:47 -0700 (PDT) [thread overview]
Message-ID: <200504292037.NAA28344@emf.net> (raw)
In-Reply-To: <Pine.LNX.4.61.0504291608410.32145@cag.csail.mit.edu> (cscott@cscott.net)
lord:
> I would expect someone to have on hand a small number of blobs that are
> different but have different hashes and, eventually, to drop said files
> into a blob-based infrastructure to wreak havoc.
cscott:
This is just ridiculous. The number of known collisions in SHA1 is
*exactly zero* at this point in time --- not guaranteed to stay that way,
of course, but generating collisions is likely to remain relatively
expensive for some time.
Blob-dbs and the low-level object system (trees, file-contents, and
changesets) are pretty fundamental things. It is likely (and
desirable) -- not guaranteed but likely (and desirable) -- that people
will invest heavily in building infrastructure that operates solely at
that level of abstraction. Arguably, that is already happening.
Simultaneously, it is very desirable that some mathemetican somewhere
will discover two bitstrings which are different but have SHA1
checksums, and then tell everyone in the world about their discovery.
My point is simply that blob-db implementations should assume that the
mathemeticians will succeed and take the small steps necessary to make
sure that those bitstrings can't be used to crash a distributed
blob-db infrastructure.
-t
next prev parent reply other threads:[~2005-04-29 20:38 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-29 0:06 Val Henson's critique of hash-based content storage systems Rob Jellinghaus
2005-04-29 19:45 ` Linus Torvalds
2005-04-29 19:52 ` Tom Lord
2005-04-29 20:17 ` C. Scott Ananian
2005-04-29 20:37 ` Tom Lord [this message]
2005-04-29 20:41 ` C. Scott Ananian
2005-04-29 20:14 ` H. Peter Anvin
2005-04-29 20:47 ` Morten Welinder
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200504292037.NAA28344@emf.net \
--to=lord@emf.net \
--cc=cscott@cscott.net \
--cc=git@vger.kernel.org \
--cc=robj@unrealities.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).