mirror of
https://github.com/tahoe-lafs/tahoe-lafs.git
synced 2025-03-29 23:05:58 +00:00
known_issues.txt: edits suggested by Brian
This commit is contained in:
parent
6dde8398fe
commit
962a53edee
@ -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
|
that different downloads using the same capability could result in
|
||||||
different files. This flaw can be exploited only by the original
|
different files. This flaw can be exploited only by the original
|
||||||
uploader of an immutable file, which means that it is not a severe
|
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
|
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
|
original uploader intended. The only issue is that you can't assume
|
||||||
not also provide the guarantee that the original uploader could have
|
that every time you use the same capability to download a file you'll
|
||||||
uploaded only one file per capability.
|
get the same file.
|
||||||
|
|
||||||
==== how to manage it ====
|
==== how to manage it ====
|
||||||
|
|
||||||
|
Loading…
x
Reference in New Issue
Block a user