- 24 Mar, 2019 1 commit
-
-
Simon Giesecke authored
Solution: define setUp/tearDown functions via SETUP_TEARDOWN_TESTCONTEXT macro where possible
-
- 20 Mar, 2019 2 commits
-
-
Simon Giesecke authored
Solution: migrate to unity and adapt users
-
Simon Giesecke authored
Solution: migrate to unity
-
- 18 Nov, 2018 1 commit
-
-
Luca Boccassi authored
Solution: do it
-
- 27 May, 2018 1 commit
-
-
Simon Giesecke authored
Solution: apply naming style
-
- 22 Mar, 2018 1 commit
-
-
Luca Boccassi authored
Solution: like for other mechanism, do not enforce strict ZAP protocol adherence unless the specific socket option is enabled with NULL auth. Add test to exercise this functionality, and fix ZAP test to set the socket option when it uses NULL auth. See: https://github.com/zeromq/pyzmq/pull/1152
-
- 02 Feb, 2018 1 commit
-
-
sigiesec authored
Solution: applied clang-format
-
- 09 Oct, 2017 1 commit
-
-
Luca Boccassi authored
Solution: add ZMQ_ZAP_ENFORCE_DOMAIN to hide backward incompatible change and make it disabled by default. In a future release that breaks API compatibility we can then switch the default to enabled in order to achieve full RFC compatibility. Fixes #2762
-
- 19 Sep, 2017 1 commit
-
-
sigiesec authored
receive an ERROR (probably because the connection is closed before) Solution: wait for client-side monitor events before closing the client socket Fixes #2705
-
- 18 Sep, 2017 4 commits
-
-
sigiesec authored
Solution: added tests
-
sigiesec authored
Solution: added test & some improvements of test utils
-
sigiesec authored
Solution: emit events as expected by tests, and refuse connections when ZAP is required but no handler started Addresses #2711 partially
-
sigiesec authored
Solution: added test case for NULL/PLAIN/CURVE
-
- 07 Sep, 2017 2 commits
-
-
Doron Somech authored
-
sigiesec authored
Solution: renamed routing_id fields in pipe_t, renamed ZMQ_CONNECT_RID to ZMQ_CONNECT_ROUTING_ID
-
- 20 Aug, 2017 2 commits
-
-
Simon Giesecke authored
Problem: test_zap_unsuccessful_status_500 and test_curve_security_with_bogus_client_credentials sometimes fail, particulary on slow/valgrind runs Solutio: relax test assertion
-
sigiesec authored
Problem: no tests for client-side events for successful handshake and authentication failure in handshake Solution: added tests for CURVE, add emitting of client-side event in curve_client_t; add ZAP code 300/500 tests for all mechanisms; suppress sending an error message for ZAP code 300
-
- 18 Aug, 2017 1 commit
-
-
sigiesec authored
Solution: redesign ZMQ_HANDSHAKE_FAILED_* events, introduce new class of ZMQ_HANDSHAKE_FAILED_AUTH events
-
- 17 Aug, 2017 3 commits