On Thu, May 03, 2001 at 10:41:30PM -0400, Tavin Cole wrote:
> Currently the full structure of an unencrypted Freenet document
> looks like this:
>
> 2 bytes: crypto key length
> X bytes: crypto key, where X == crypto key length
> remainder: actual file data
>
> This allows the requesting client to check that it in fact has the
> correct decryption key, although the java clients don't actually
> do this.
>
It should. The whole point here wsa to have a mechanism in place to force
encryption of files.
> The key specs are changing in 0.4, mainly in order to make the
> storables untamperable. While we are doing this, I believe we
> should also take the opportunity to move Metadata-length out of
> the storables. One way to do this would be to encode it into
> the document structure (#1):
>
> 2 bytes: crypto key length
> X bytes: crypto key
> 8 bytes: metadata length
> remainder: actual file data
>
> However, at least as far as the java implementation goes, this is
> rather difficult to deal with in practice. Actually even having
> the crypto key at the beginning of the document makes things
> unnecessarily difficult.
Why?
And why expose any more information to the node than it needs?
Scott
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 232 bytes
Desc: not available
URL:
<https://emu.freenetproject.org/pipermail/devl/attachments/20010503/860c7ddb/attachment.pgp>
