From: Tom Lord <lord@emf.net>
To: git@vger.kernel.org
Cc: robj@unrealities.com
Subject: Re: Val Henson's critique of hash-based content storage systems
Date: Fri, 29 Apr 2005 12:52:43 -0700 (PDT) [thread overview]
Message-ID: <200504291952.MAA27541@emf.net> (raw)
In-Reply-To: <Pine.LNX.4.58.0504291221250.18901@ppc970.osdl.org> (message from Linus Torvalds on Fri, 29 Apr 2005 12:45:07 -0700 (PDT))
I wouldn't expect outright successful attacks like forged replacements
for arbitrary files.
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.
So: a way to locally mark a given checksum as "controversial" seems
prudent, to me (hence, support for such in my blob-db code/spec).
-t
next prev parent reply other threads:[~2005-04-29 19:47 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 [this message]
2005-04-29 20:17 ` C. Scott Ananian
2005-04-29 20:37 ` Tom Lord
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=200504291952.MAA27541@emf.net \
--to=lord@emf.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).