9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: <philw@entrisphere.com>
To: <9fans@cse.psu.edu>
Subject: RE: [9fans] compare-by-hash
Date: Sat, 31 May 2003 16:58:02 -0700	[thread overview]
Message-ID: <6A0F443DA784CE4E864740DD14BC16BB1003FA@otto.int.entrisphere.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 664 bytes --]

and then what?

	-----Original Message----- 
	From: Russ Cox [mailto:rsc@plan9.bell-labs.com] 
	Sent: Sat 5/31/2003 4:54 PM 
	To: 9fans@cse.psu.edu 
	Cc: 
	Subject: Re: [9fans] compare-by-hash
	
	

	The paper seems correct on most things, but is unfair to Venti.
	
	Venti is closer to hashing than compare-by-hash.
	Venti does look for SHA1 hash collisions -- once a block with a
	particular SHA1 hash has been written, you can't write any
	others.  Therefore you can't possibly end up thinking there are
	two different blocks stored on the same server and represented
	by the same SHA1 hash -- the store of the second will fail!
	
	Russ
	


[-- Attachment #2.1: Type: text/plain, Size: 268 bytes --]

The following attachment had content that we can't
prove to be harmless.  To avoid possible automatic
execution, we changed the content headers.
The original header was:

	Content-Type: application/ms-tnef;
	name="winmail.dat"
	Content-Transfer-Encoding: base64

[-- Attachment #2.2: winmail.dat.suspect --]
[-- Type: application/octet-stream, Size: 3710 bytes --]

             reply	other threads:[~2003-05-31 23:58 UTC|newest]

Thread overview: 44+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-05-31 23:58 philw [this message]
2003-06-01  0:00 ` Russ Cox
2003-06-01  1:15   ` northern snowfall
2003-06-01  0:23     ` Russ Cox
2003-06-01  1:23       ` northern snowfall
2003-06-01  0:24     ` Dan Cross
2003-05-31 23:49       ` Skip Tavakkolian
2003-06-01  5:52         ` Dan Cross
2003-06-01  8:57           ` Charles Forsyth
2003-06-01  9:06             ` lucio
2003-06-01  9:25               ` lucio
2003-06-01 15:36                 ` David Presotto
2003-06-01 16:24                   ` David Presotto
2003-06-02  4:14                     ` lucio
2003-06-02  4:03                   ` lucio
2003-06-01 22:55             ` Geoff Collyer
2003-06-01  0:28     ` William Josephson
2003-06-01  1:46       ` northern snowfall
2003-06-01  1:38         ` William K. Josephson
2003-06-01  1:57           ` Scott Schwartz
2003-06-01  2:58           ` northern snowfall
2003-06-01  2:57             ` W. Josephson
2003-06-01  4:07               ` northern snowfall
2003-06-01 15:11                 ` boyd, rounin
2003-06-02 11:37     ` Sam
2003-06-02 12:41       ` boyd, rounin
  -- strict thread matches above, loose matches on Subject: below --
2003-08-03  4:39 Andrew Simmons
2003-07-31 17:24 Joel Salomon
2003-07-31 17:50 ` andrey mirtchovski
2003-07-31 17:51 ` Sape Mullender
2003-07-31 17:53 ` rog
2003-07-31 18:03 ` jmk
2003-08-01  2:45 ` Joel Salomon
2003-08-01  2:52   ` Geoff Collyer
2003-08-01  3:42     ` jmk
2003-08-01  4:12       ` Geoff Collyer
2003-08-01 15:23       ` Jack Johnson
2003-08-01  9:03     ` Anthony Mandic
2003-08-01 15:11     ` Jack Johnson
2003-08-01  9:02 ` Douglas A. Gwyn
2003-05-31 23:48 Taj Khattra
2003-05-31 23:48 ` Charles Forsyth
2003-05-31 23:50 ` Charles Forsyth
2003-05-31 23:54 ` Russ Cox

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=6A0F443DA784CE4E864740DD14BC16BB1003FA@otto.int.entrisphere.com \
    --to=philw@entrisphere.com \
    --cc=9fans@cse.psu.edu \
    /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.
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 NNTP newsgroup(s).