/me thinks... indeed, the server doesn't need to know its own public key since it never shares it nor uses it for encrypting/decrypting. Do you think it's simpler for the user to always set both keys on all CURVE sockets, or to know this distinction?
On Wed, Oct 23, 2013 at 12:38 PM, Peter Kleiweg <[email protected]> wrote: > Pieter Hintjens schreef op de 23e dag van de wijnmaand van het jaar 2013: > >> For both clients and servers one must set public and secret keys; for >> clients one additionally sets the server's public key, and for servers >> one tells libzmq it is a server. > > I got examples working without setting the public key on the > server (modified from your examples in "Using ZeroMQ Security > (part 2)"). > > All I do for server is: > > SetCurveServer(1) > SetCurveSecretkey(server_secret_key) > > For client, I do: > > SetCurveServerkey(server_public_key) > SetCurvePublickey(client_public_key) > SetCurveSecretkey(client_secret_key) > > > > > -- > Peter Kleiweg > http://pkleiweg.home.xs4all.nl/ > _______________________________________________ > zeromq-dev mailing list > [email protected] > http://lists.zeromq.org/mailman/listinfo/zeromq-dev -- - Pieter Hintjens CEO of iMatix.com Founder of ZeroMQ community blog: http://hintjens.com _______________________________________________ zeromq-dev mailing list [email protected] http://lists.zeromq.org/mailman/listinfo/zeromq-dev
