Well any client can pick their own keypair, so unless you have the public key
then it's moot. If the client claims to be billgates and signs their message
(and you have their pubkey) then they're authenticated, no?
On Tuesday, December 31, 2013 7:01 AM, Drew Crawford d...@sealedabstract.com
Yes, if the client claims to be billgates and signs their message with the
known publickey, then they’re authenticated. The question is, did they do
this? Or not?
Let me now be more detailed about the problem. The problem is to correlate an
incoming message with a publickey of the sender.
Hey folks,
I’ve got a REQ-ROUTER architecture where clients (with a REP socket) connect to
a server (with a ROUTER socket). This connection is authenticated via CURVE.
I need to figure out some person/username/unique identifier that is associated
with the incoming REQ. There are a couple of
Have you thought about a custom frame at the top of your message?
Or the clients can set their own custom identity if they have unique names.
On Tuesday, December 31, 2013 6:51 AM, Drew Crawford d...@sealedabstract.com
wrote:
Hey folks,
I’ve got a REQ-ROUTER architecture where clients
Well if I allow just any client to claim to be billgates that’s not going to be
very secure…
…or did I misunderstand your proposal?
On Dec 31, 2013, at 12:56 AM, Amir Taaki zgen...@yahoo.com wrote:
Have you thought about a custom frame at the top of your message?
Or the clients can set
