Try to explain things
[Imported from Trac: page NewCaps/Rainhill, version 9]
parent
b96f3af187
commit
1a83df2084
|
@ -1,5 +1,15 @@
|
||||||
This is about What Could Go Wrong with the "Rainhill 3" immutable file caps: <http://jacaranda.org/tahoe/immutable-rainhill-3.svg>
|
This is about What Could Go Wrong with the "Rainhill 3" immutable file caps: <http://jacaranda.org/tahoe/immutable-rainhill-3.svg>
|
||||||
|
|
||||||
|
Wayback Machine link: <https://web.archive.org/web/*/http://jacaranda.org/tahoe/>*
|
||||||
|
|
||||||
|
Explanation by ccx:
|
||||||
|
|
||||||
|
> What I assume this to be is an encoding scheme for immutable directories that allows deriving deep-verify capability so that whole directory tree below can be verified recursively.
|
||||||
|
>
|
||||||
|
> This is done by encoding separately the readcaps of items contained in the directory (Plain_R) and verifycaps of the same items (Plain_V).
|
||||||
|
>
|
||||||
|
> By applying this scheme to the plaintexts together with convergence secret (CS) and encoding parameters you will get two encryption keys EncK_R and EncK_V for each part respectively.
|
||||||
|
|
||||||
(<http://jacaranda.org/tahoe/immutable-rainhill-3.png> or [download the attached SVG](../raw/attachments/NewCaps/Rainhill/immutable-rainhill-3.svg) if your browser does not correctly handle SVG.)
|
(<http://jacaranda.org/tahoe/immutable-rainhill-3.png> or [download the attached SVG](../raw/attachments/NewCaps/Rainhill/immutable-rainhill-3.svg) if your browser does not correctly handle SVG.)
|
||||||
|
|
||||||
![](attachments/NewCaps/Rainhill/immutable-rainhill-3.svg)
|
![](attachments/NewCaps/Rainhill/immutable-rainhill-3.svg)
|
||||||
|
|
Loading…
Reference in a new issue