Authentication and Encryption

[digitalextremist]

In early analysis of 0MQ security underlying DCell, it seems the best way to bring authentication and encryption to DCell is by implementing CurveZMQ:

https://github.com/zeromq/libcurve

Research the API; if possible and wise: integrate libcurve to provide security for DCell.

• Research API
• Write integration
• Test implementation
• Write applicable tests
• Update documentation
• Write example code

Coverage:

• Encryption
• Authentication

[digitalextremist]

@tarcieri / @chuckremes -- In ZMQland, is there ever a time that a:

• Subscribing socket
• Pulling socket, or
• Requesting socket

...would ever be a server?

[digitalextremist]

It seems like the whole concept of server vs. client is a misnomer in this case.

Whoever has the secret is the receiver of the connection, and therefore the server but the client doesn't seem to be read only in every case.

[Asmod4n]

Authentication and Encryption is already there: https://github.com/Asmod4n/celluloid-zmq-zap/blob/master/examples/curve_redis.rb

Its just that ZAP is broken, or at last it was when i was testing it.
When a client connects with wrong credentials the server will storm the handler forever and there is no error or anything propagated anywhere. @digitalextremist @tarcieri @chuckremes

[Asmod4n]

With Router(Server) and Dealer(Client) sockets after sending a message from a dealer to a router they both can exchange messages in any way, fully async.

http://zguide.zeromq.org/page:all#advanced-request-reply
http://zguide.zeromq.org/page:all#The-DEALER-to-ROUTER-Combination

[Asmod4n]

czmq is about to get official ruby bindings, so my wrapper won't receive any updates anymore: https://github.com/zeromq/czmq/tree/master/bindings/ruby/lib/czmq/ffi

[digitalextremist]

Will reapproach once bindings land.