implement plaintext/crypttext merkle trees #64

New Issue

warner · 2007-06-07T19:12:29Z

warner commented

2007-06-07 19:12:29 +00:00

the "thingA" block (scheduled to be renamed in #62) should include the root hashes of a pair of merkle trees: one computed over the segments of plaintext, and another computed over the segments of crypttext.

This will give us the ability to validate individual segments of plaintext (such that we can detect corrupted encryption keys, or bugs in FEC or decryption). At the moment the only form of validation which can detect such problems is the FileID, which cannot be computed until the entire file has been downloaded.

The hash trees themselves are stored in the Bucket, and accessed with a get/set method pair for each tree. All buckets store the same data.

For a first cut, we'll retrieve all the hashes at the same time. A later enhancement should be to retrieve only the hashes we actually need for any given block, to improve the alacrity.

the "thingA" block (scheduled to be renamed in #62) should include the root hashes of a pair of merkle trees: one computed over the segments of plaintext, and another computed over the segments of crypttext. This will give us the ability to validate individual segments of plaintext (such that we can detect corrupted encryption keys, or bugs in FEC or decryption). At the moment the only form of validation which can detect such problems is the FileID, which cannot be computed until the entire file has been downloaded. The hash trees themselves are stored in the Bucket, and accessed with a get/set method pair for each tree. All buckets store the same data. For a first cut, we'll retrieve all the hashes at the same time. A later enhancement should be to retrieve only the hashes we actually need for any given block, to improve the alacrity.

warner added the

labels 2007-06-07 19:12:29 +00:00

warner added this to the 0.3.0 milestone 2007-06-07 19:12:29 +00:00

warner self-assigned this 2007-06-07 19:12:29 +00:00

warner commented

2007-06-07 20:37:59 +00:00

this is fully implemented now (I think changeset:c81f2b01ffc6d6c7 was the last fix). It needs more exhaustive unit tests to exercise the failure cases, but that's not a blocker for 0.2.1.