-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On Thu, May 7, 2009 at 2:32 PM, Jusa Saari wrote: > On Thu, 07 May 2009 00:59:36 +0100, Matthew Toseland wrote: > >> (Easy) - MHKs (or DHKs) - redundant CHKs for the top block of a splitfile >> (no, I don't like RHK, it sounds too much like RSK, and R stands for >> Revocable not Redundant). (Reasonably easy) > > Trivial, actually. Simply add a field that can contain a string of letters > or numbers but doesn't affect anything (except the CHK) to the metadata, > generate multiple versions of the top block by populating the field with > different strings, and have some kind of way to paste the resulting list > of keys into a single string - something like CHK at key1;key2;key3/filename. > Sure, they'll be _long_, but it's not like anyone types keys by hand > anyway. > > No reason to add a new keytype for this, IMHO. Something as simple as "1111" or "2222" or "3333" would be enough to change the hash of the CHK and would be a known value so we could recreate the missing CHKs and reinsert them, yes? ie we have a MHK at key1blahblah, key2blahblah, key3blahblah/somefilename.avi (or CHK instead of MHK, whatever works) We are not able to find key1 or key3, but we are able to retrieve key2 and successfully download the entire file. Then as part of the FEC healing mechanism we can recreate key1 and key3 just by taking key2 and changing the field from "2222" to "1111" and another with "3333" and insert them back into the network. Does this sound feasible? - -- I may disagree with what you have to say, but I shall defend, to the death, your right to say it. - Voltaire Those who would give up Liberty, to purchase temporary Safety, deserve neither Liberty nor Safety. - Ben Franklin -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (MingW32) Comment: Use GnuPG with Firefox : http://getfiregpg.org (Version: 0.7.5) iEYEARECAAYFAkoDkNsACgkQ4esu1mlKOs+zOACfX0dL3+Xwg5sHcGpJHd4H2j7i o5UAn1t1qLVpnM1MwSvCRXLoyBPeKL6m =D/3c -----END PGP SIGNATURE-----
