You can set the ZMQ_IDENTITY sock opt on the client prior to connecting.
> On Dec 31, 2013, at 6:18 AM, Nicolas Delaby <[email protected]> wrote: > > > > Le 31/12/2013 03:32, Pieter Hintjens a écrit : >> >> >> You don't authenticate a peer based on its identity. You authenticate >> based on public key and optionally the server socket domain. ZAP >> authentication happens before any recv() and you cannot depend on any >> correlation between the two, except any recv() delivers messages from >> an authenticated sender. > Hi Pieter, > My need is the following: I need to know who is sending the message I'm > reading from ROUTER. This is important for me because, the ROUTER might > sometimes initiate a request/response exchange, not only reply to > requests. Thus, to reach the right recipient, I need its socket id. > It means I need, somehow, to maintain a mapping > public_key:socket_identity, because I only have the public_key beforehand. > > Nicolas > > -- > > Nicolas Delaby > http://ticosax.free.fr/ > > _______________________________________________ > zeromq-dev mailing list > [email protected] > http://lists.zeromq.org/mailman/listinfo/zeromq-dev _______________________________________________ zeromq-dev mailing list [email protected] http://lists.zeromq.org/mailman/listinfo/zeromq-dev
