From: Zooko O'Whielacronx Date: Mon, 21 Jul 2008 17:44:06 +0000 (-0700) Subject: known_issues.txt: edits suggested by Brian X-Git-Tag: allmydata-tahoe-1.2.0~9 X-Git-Url: https://git.rkrishnan.org/specifications/something?a=commitdiff_plain;h=962a53edeea56a4c5ce3df3162e4ccca0f3979ac;p=tahoe-lafs%2Ftahoe-lafs.git known_issues.txt: edits suggested by Brian --- diff --git a/docs/known_issues.txt b/docs/known_issues.txt index fc2634ab..39c0b643 100644 --- a/docs/known_issues.txt +++ b/docs/known_issues.txt @@ -14,11 +14,11 @@ produce more than one immutable file matching the same capability, so that different downloads using the same capability could result in different files. This flaw can be exploited only by the original uploader of an immutable file, which means that it is not a severe -vulnerability. You can still rely on the integrity check to make sure +vulnerability: you can still rely on the integrity check to make sure that the file you download with a given capability is a file that the -original uploader intended. The flaw is that the integrity check does -not also provide the guarantee that the original uploader could have -uploaded only one file per capability. +original uploader intended. The only issue is that you can't assume +that every time you use the same capability to download a file you'll +get the same file. ==== how to manage it ====