From: Brian Warner <warner@allmydata.com>
Date: Tue, 30 Oct 2007 01:14:51 +0000 (-0700)
Subject: docs/mutable.txt: we need readkey IV
X-Git-Tag: allmydata-tahoe-0.7.0~349
X-Git-Url: https://git.rkrishnan.org/listings/provisioning?a=commitdiff_plain;h=64f7183157669b0d898350ccb218d7f157246dd8;p=tahoe-lafs%2Ftahoe-lafs.git

docs/mutable.txt: we need readkey IV
---

diff --git a/docs/mutable.txt b/docs/mutable.txt
index 82b38b7d..845f88b9 100644
--- a/docs/mutable.txt
+++ b/docs/mutable.txt
@@ -484,10 +484,12 @@ provides explicit support for revision identifiers and branching.
 
 == TODO ==
 
+add IV, use it by hashing the long-term readkey with the IV to generate the
+per-version readkey.
 
 improve allocate-and-write or get-writer-buckets API to allow one-call (or
 maybe two-call) updates. The challenge is in figuring out which shares are on
-which machines.
+which machines. First cut will have lots of round trips.
 
 (eventually) define behavior when seqnum wraps. At the very least make sure
 it can't cause a security problem. "the slot is worn out" is acceptable.