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

[Nick Mathewson]

On Wed, Mar 30, 2005 at 04:39:34PM +0200, Laurent Fousse wrote:
[...] 
> > The "tag" (or "decoding handle" is indeed visible in the reply
> > message as the client receives it; Mixminion should handle it for
> > you.
> 
> Hum. I think we need to get this "tag" before we call the ClientAPI,
> and letting Mixminion handle it for us is not enough.
> nym3-client should support different accounts, so (presumably) one
> SURB-keyring for each account. When we create the ClientEnv object
> we need to pass the right keyring to it.

No, look at how keyrings work (mixminion.ClientUtils.Keyring): each
keyring can store keys for multiple identities, and Mixminion can
search through the keyring for the identity that matches.  You
shouldn't need to touch the decoding handle at all.  Once you've
decoded the payload of a message, Mixminion can tell you which
identity it's for.

(What would you *do* with the decoding handle if you had it?  I can't
see what you need it for.)

> Is SURB.getDecodingHandle() usable on a reply message (I guess no) ?

No.  It is only useable on SURBs; and reply messages are not reply
blocks.

> If you say we can just use one shared SURB-keyring for all accounts
> and it implies no anonymity problem to the user, that's certainly fine
> with me.

That's right.  Within the keyring, each identity gets its own separate
set of keys.

> > > 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 far as ClientAPI is concerned, the documentation is the source,
> right?

Currently, yes.  Once it starts getting written, however, the
documentation will only consist of the class/function declarations and
their documentation strings.  Implementation source will not be a part
of the documentation.


Hope this helps,
-- 
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/20050330/ed675e1e/attachment.pgp