- 24 Mar, 2019 1 commit
-
-
Simon Giesecke authored
Solution: remove s_send(more) and replace all uses
-
- 23 Mar, 2019 2 commits
-
-
Simon Giesecke authored
Solution: remove and add where needed
-
Simon Giesecke authored
Solution: use unity assertions instead
-
- 16 Mar, 2019 1 commit
-
-
Simon Giesecke authored
Solution: migrate to Unity and separate test_security_no_zap_handler
-
- 27 May, 2018 1 commit
-
-
Simon Giesecke authored
Solution: apply naming style
-
- 14 May, 2018 1 commit
-
-
Simon Giesecke authored
Solution: Use fd_t
-
- 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
-
- 19 Sep, 2017 1 commit
-
-
sigiesec authored
Solution: use "routing_id" instead
-
- 01 May, 2017 1 commit
-
-
Luca Boccassi authored
Solution: use ZMQ_LAST_ENDPOINT in most places. This alllows running tests in paralle, and on over-booked shared machines where many of the ports would be already in use. Keep 3 tests with an hardcoded port, as there are some code paths that require it (eg: connect before bind), but list those ports in tests/testutil.hpp as macros so that they do not overlap and still allow parallel runs. These changes were inspired by a patch uploaded to Ubuntu by the package maintainer, Steve Langasek <steve.langasek@ubuntu.com>. Thank you Steve!
-
- 12 Feb, 2016 1 commit
-
-
Pieter Hintjens authored
There were numerous small issues with test cases: - some lacked the right source file header - some were not portable at all - some were using internal libzmq APIs (headers) Solution: fixed and cleaned up.
-
- 06 Feb, 2016 1 commit
-
-
Michael authored
-
- 28 Jan, 2016 1 commit
-
-
Constantin Rack authored
Solution: update to 2016
-
- 02 Jun, 2015 1 commit
-
-
Pieter Hintjens authored
Of course people still "can" distributed the sources under the LGPLv3. However we provide COPYING.LESSER with additional grants. Solution: specify these grants in the header of each source file.
-
- 07 May, 2015 1 commit
-
-
Dan Riegsecker authored
When targeting a version of Windows less than Windows Vista, the security tests fail to build. Added a check for Windows version and substituted inet_pton for inet_addr. Fixes libzmq issue #1396.
-
- 30 Jan, 2015 1 commit
-
-
Pieter Hintjens authored
Solution: raise timeouts from 100-150 msec to 250 msec
-
- 22 Jan, 2015 1 commit
-
-
Pieter Hintjens authored
Solution: update for 2015 Fixes #1320
-
- 03 Dec, 2014 3 commits
- 02 May, 2014 2 commits
-
-
Pieter Hintjens authored
-
Pieter Hintjens authored
- also prioritize ZAP metadata over ZMTP metadata in case application uses same names.
-
- 29 Apr, 2014 2 commits
-
-
Pieter Hintjens authored
- additional messages to help people debugging security errors
-
Pieter Hintjens authored
Has some bits commented out due to #939, now work. Note: there is an issue in libzmq when binding/unbinding or connecting/disconnecting (I did not investigate deeper) the same socket several times. Even closing the socket with zero linger, zmq_ctx_term will block. The workaround in this test case is to close the sockets for each test step.
-
- 02 Jan, 2014 1 commit
-
-
Pieter Hintjens authored
-
- 18 Sep, 2013 1 commit
-
-
Markus Rothe authored
-
- 17 Sep, 2013 2 commits
-
-
Pieter Hintjens authored
-
Pieter Hintjens authored
-
- 16 Sep, 2013 1 commit
-
-
Pieter Hintjens authored
* ZAP handler thread was not getting time to start up * Code now creates and binds handler socket in parent thread and passes the socket to the zap_handler, so this always gets the authentication requests.
-
- 15 Sep, 2013 1 commit
-
-
Pieter Hintjens authored
* Removed redundant Z85 code and include files from project * Simplified use of headers in test cases (now they all just use testutil.hpp) * Export zmq_z85_encode() and zmq_z85_decode() in API * Added man pages for these two functions
-
- 12 Sep, 2013 1 commit
-
-
Pieter Hintjens authored
-
- 09 Sep, 2013 1 commit
-
-
Pieter Hintjens authored
* This is passed to the ZAP handler in the 'domain' field * If not set, or empty, then NULL security does not call the ZAP handler * This resolves the phantom ZAP request syndrome seen with sockets where security was never intended (e.g. in test cases) * This means if you install a ZAP handler, it will not get any requests for new connections until you take some explicit action, which can be setting a username/password for PLAIN, a key for CURVE, or the domain for NULL.
-
- 02 Sep, 2013 1 commit
-
-
Pieter Hintjens authored
- Split off NULL security check from PLAIN - Cleaned up test_linger code a little - Got all tests to pass, added TODOs for outstanding issues - Added ZAP authentication for NULL test case - NULL mechanism was not passing server identity - fixed - cleaned up test_security_plain and removed option double-checks (made code ugly) - lowered timeout on expect_bounce_fail to 150 msec to speed up checks - removed all sleeps from test_fork and simplified code (it still passes :-)
-