----- Original Message -----
From: "Gianni Johansson" <[email protected]>


> I thought I had mailed this link to the list a while back, but here it is
> again.
>
>
http://cvs.sourceforge.net/cgi-bin/viewcvs.cgi/freenet/Contrib/gj/FCP-FEC.tx
t
>
> This whole episode with inserting metadata into data blocks should have
never
> happened.  I tried to get the following changes to the SplitFile spec made
two
> weeks ago.
>
http://hawk.freenetproject.org:8080/pipermail/devl/2003-January/003373.html

<snip>

> 1) THIS SHOULD BE ADDED TO THE SPEC.

-- 1) Specification of cipher used for all block CHKs
-- SplitFile.BlockCipher=TwoFish

I am wondering why exactly this should be added. It aids with healing given
abilities a client does not usually have. We cannot choose the block cipher
to encrypt with. (unless things have changed)

Counterproposal:
We could make the blanket statement that all the blocks of the splitfile
need to be the same encoding. It would have the same end result, assuming
that atleast one block was retrievable.

Additional things to do with counterproposal for people not using your fcp:
We could do is modify the fcp command to insert with an optional
[BlockCipher=cipher]
Then perhaps go as far as adding a fcp command which returns the metadata
for a given key rather than the data (as in the real metadata, not the
metadata which is used for control docs) Of course, this may make fcp
clients and the node too closely linked for specific versions.

<snip>

> If you have objections, please present a counter proposal that fully
> addresses healing reinsertion.
>
> --gj

-Mathew


_______________________________________________
devl mailing list
devl at freenetproject.org
http://hawk.freenetproject.org:8080/cgi-bin/mailman/listinfo/devl

Reply via email to