- 31 Dec, 2016 1 commit
-
-
Luca Boccassi authored
Solution: check that the expected handshake success or failure events are triggered in the curve security unit test
-
- 01 Mar, 2016 1 commit
-
-
Pieter Hintjens authored
Libsodium has started returning -1 in some cases. Solution: allow and handle error returns from these calls. Fixes #1831
-
- 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.
-
- 11 Feb, 2016 1 commit
-
-
Pieter Hintjens authored
It's unclear which we need and in the source code, conditional code treats tweetnacl as a subclass of libsodium, which is inaccurate. Solution: redesign the configure/cmake API for this: * tweetnacl is present by default and cannot be enabled * libsodium can be enabled using --with-libsodium, which replaces the built-in tweetnacl * CURVE encryption can be disabled entirely using --enable-curve=no The macros we define in platform.hpp are: ZMQ_HAVE_CURVE 1 // When CURVE is enabled HAVE_LIBSODIUM 1 // When we are using libsodium HAVE_TWEETNACL 1 // When we're using tweetnacl (default) As of this patch, the default build of libzmq always has CURVE security, and always uses tweetnacl.
-
- 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
- 07 Nov, 2014 1 commit
-
-
Constantin Rack authored
-
- 19 Sep, 2014 1 commit
-
-
Pieter Hintjens authored
Solution: accept only the mechanism defined by the socket options. I've not tested this yet, so it's a speculative fix.
-
- 18 Sep, 2014 1 commit
-
-
Pieter Hintjens authored
Solution: check that it rejects attempts to connect to a CURVE server using NULL or PLAIN client.
-
- 12 Aug, 2014 1 commit
-
-
Pieter Hintjens authored
Solution: change setsockopts on printable keys to expect 41, nor 40 bytes. Code still accepts 40 bytes for compatibility, and copies the key to a well-terminated string before using it. Fixes #1148
-
- 16 Mar, 2014 1 commit
-
-
Pieter Hintjens authored
-
- 02 Jan, 2014 1 commit
-
-
Pieter Hintjens authored
-
- 30 Sep, 2013 1 commit
-
-
Pieter Hintjens authored
* Added new man page for this * Added test case, in tests/test_security_curve.cpp * Noted in zmq_utils.h that these methods are documented
-
- 18 Sep, 2013 1 commit
-
-
Markus Rothe authored
-
- 17 Sep, 2013 4 commits
-
-
Pieter Hintjens authored
This reverts commit bfd472f9.
-
Pieter Hintjens authored
This reverts commit 1206f457.
-
Laurent Alebarde authored
-
Laurent Alebarde 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 3 commits
-
-
Laurent Alebarde authored
-
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
-
Pieter Hintjens authored
-
- 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.
-
- 06 Sep, 2013 1 commit
-
-
Richard Newton authored
-
- 05 Sep, 2013 1 commit
-
-
Pieter Hintjens authored
-
- 04 Sep, 2013 1 commit
-
-
Pieter Hintjens authored
* Command names changed from null terminated to length-specified * Command frames use the correct flag (bit 2) * test_stream acts as test case for command frames * Some code cleanups
-
- 02 Sep, 2013 3 commits
-
-
Pieter Hintjens authored
- if ZAP server returns anything except 200, connection is closed - all security tests now pass correctly - test_security_curve now does proper client key authentication using test key - test_security_plain now does proper password authentication
-
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 :-)
-
Pieter Hintjens authored
-
- 31 Aug, 2013 1 commit
-
-
MinRK authored
adds expect_bounce_fail test function which is like bounce, but fails if messages arrive.
-
- 20 Aug, 2013 1 commit
-
-
Jeremy Rossi authored
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.
-
- 17 Aug, 2013 1 commit
-
-
Richard Newton authored
-