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

[Nick Mathewson]

On Tue, Mar 29, 2005 at 10:36:39PM +0200, Laurent Fousse wrote:
> 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.

By "returning SURB", you mean a reply message, right?  The "tag" (or
"decoding handle" is indeed visible in the reply message as the client
receives it; Mixminion should handle it for you.

> 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 ?

(There shouldn't be a need to "assume" anything here -- ClientAPI
should do what its documentation says.  If the documentation isn't
clear on some point, please let me know so I can fix it.)

As ClientAPI currently stands, the idea is that you provide an
identity string when you call "generateSURB" or "generateSURBS", and
later you get that identity back when you call "getSURBIdentity" on
the decoded packets.  Is this about what you wanted?


-- 
Nick Mathewson
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 652 bytes
Desc: not available
Url : http://lists.noreply.org/pipermail/nym3-devel/attachments/20050329/e141fd58/attachment.pgp