#753: use longer storage index / cap for collision resistance
---------------------------+------------------------------------------------
Reporter: warner | Owner:
Type: defect | Status: new
Priority: major | Milestone: undecided
Component: code-encoding | Version: 1.4.1
Keywords: | Launchpad_bug:
---------------------------+------------------------------------------------
Comment(by zooko):
P.S. Oh, what I wrote about people choosing whatever storage index they
want is possibly confused because I'm conflating two ideas into the word
"storage index". Let's talk about those two uses as "server selector" and
"file identifier". The former is how you decide which servers you're
going to use (either when uploading a file for the first time or when
using a cap to find a file that's already up there). The latter is how
you tell a storage server which of the shares that it has are the shares
that you are currently interested in. I currently think that the verify
cap is a good thing to use for the latter role, but perhaps not for the
former.
--
Ticket URL: <http://allmydata.org/trac/tahoe/ticket/753#comment:2>
tahoe-lafs <http://allmydata.org>
secure decentralized file storage grid
_______________________________________________
tahoe-dev mailing list
[email protected]
http://allmydata.org/cgi-bin/mailman/listinfo/tahoe-dev
