> So, it sounds like the way to go is to have a Storable.Client-data which > would be presumably a Base64 string-encoding of an encrypted byte array. > > Should it decrypt to a (alphabetized) FieldSet or to a binary structure? > > #1: decrypts to -- > Metadata-length=<hex> > Symmetric-key=<hex> > End > #2: decrypts to -- > <2 bytes crypto key length><crypto key><8 bytes metadata length>
Definitely #1. You can't put symmetric-key in this field, however, for obvious reasons. > > Either way we can pad it to a decent length by repeating some hash > function of the data. Thats not necessary, you can just throw random bytes in the message's trailing field. -------------- 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/20010504/f8c32fcb/attachment.pgp>
