10 Commits

Author	SHA1	Message	Date
Jeremy Rossi	19ca8a0fc0	Add the Socket Identity info to the ZAP Messages ... This change adds the socket identity infomartion from the socket to the zap frames. In doing this the ZAP is able preform different operations based on different sockets. This is not compaitable with the current ZAP RFC, but that can be updated. As the ZAP rfc is currently draft for I did not change the version number. Tests also modified and passing.	2013-08-20 13:48:05 -04:00
Richard Newton	a83baa9b0b	Fix up threading code from port tests to windows.	2013-08-17 14:23:22 +01:00
Richard Newton	7f74fc7c99	Port tests to windows and add to cmake build.	2013-08-17 13:43:45 +01:00
Martin Hurton	53bc53da04	Update PLAIN mechanism to the latest ZAP revision	2013-07-18 10:59:34 +02:00
Pieter Hintjens	7832addd20	Updated security mechanisms to use variable-length commands ... RFC23, RFC24, RFC26 now use variable-length command names that end in null octet (valid C strings) instead of fixed-length space padded strings.	2013-06-28 11:42:54 +02:00
Pieter Hintjens	6ff51ee909	Updated ZAP request for changed protocol draft ... - username and password sent as two string frames - fixed test case to match	2013-06-07 15:50:36 +02:00
Martin Hurton	2928c91a6d	Implement ZAP and integrate it with PLAIN mechanism	2013-06-06 13:28:21 +02:00
Pieter Hintjens	f06abca046	Disable failing test for now	2013-05-17 17:26:54 +01:00
Pieter Hintjens	f909b9c722	plain_mechanism now uses options.as_server ... - we need to switch to PLAIN according to options.mechanism - we need to catch case when both peers are as-server (or neither is) - and to use username/password from options, for client	2013-05-17 17:21:59 +01:00
Pieter Hintjens	e1f797b048	Added configuration for PLAIN security ... * ZMQ_PLAIN_SERVER, ZMQ_PLAIN_USERNAME, ZMQ_PLAIN_PASSWORD options * Man page changes to zmq_setsockopt and zmq_getsockopt * Man pages for ZMQ_NULL, ZMQ_PLAIN, and ZMQ_CURVE * Test program test_security	2013-05-15 17:55:21 +02:00