Maybe I should wait another 5 minutes so you can answer the question :-) Indeed, there is no support for configuring CURVE security on the zproxy sockets.
Two options. A is to add this, which is a fun exercise for someone who wants to explore how CZMQ actors work. B, use zmq_proxy as you were before, using zsock_resolve () to get the ZMQ socket handle. On Mon, Apr 20, 2015 at 11:54 AM, Alan Ward <[email protected]> wrote: > > Hi again, > > > > OK. Having delved a bit deeper it looks like I should be using zproxy rather > than zmq_proxy. > > > > I now have a problem in that I can’t determine how to connect my frontend > socket with CURVE security as the socket I wish to secure is within zproxy. > > > > Thanks > > Alan > > > > > > > > From: [email protected] > [mailto:[email protected]] On Behalf Of Alan Ward > Sent: 20 April 2015 09:12 > To: [email protected] > Subject: [zeromq-dev] zmq_proxy problem > > > > Hi, > > > > I have a system that has been using zmq_proxy for a while to distribute work > across a number of worker processes.. > > > > It was using zsocket etc. > > > > I am in the process of upgrading the system to use zsock, zactor etc and all > is going well – except that zmq-proxy is no longer working. > > > > Apart from the change to zsock the code has not changed and zmq_proxy is just > falling through with no error message. > > > > The frontend is a normal tcp socket from an external client; the backed is a > set of 3 ipc sockets. > > > > Any ideas? > > > > Thanks, > > Alan > > > > > > > _______________________________________________ > 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
