[Nym3-devel] SURBs, tag, and all that.

[Laurent Fousse]

Hi,

I think there are still some technical issues left before we can
safely go on writing the client part of nym3 (I would say the client
part is the least advanced right now).

Specifically, I'm still confused about the "tag" mentioned in
E2E-spec.txt, and wondering how nym3's client is supposed to deal with
incoming messages — is the tag from a returning SURB readable prior to
any decryption ? If that's the case we can use that information to
know for which account a given message is.

Can we assume that ClientAPI will deal with SURB-level encryption,
packet fragmentation, giving the calling program the assembled and
decrypted message and an indication of which key was used, so we can
relate the message back to the appropriate account ?
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: Digital signature
Url : http://lists.noreply.org/pipermail/nym3-devel/attachments/20050329/351ce80e/attachment.pgp