- 31 Oct, 2013 1 commit
-
-
Mark Barbisan authored
-
- 28 Oct, 2013 2 commits
-
-
Pieter Hintjens authored
* The ZMQ_ROUTER_RAW API was deprecated in favor of ZMQ_STREAM * Same issue hit router.cpp, which I've fixed
-
MinRK authored
-
- 23 Oct, 2013 1 commit
-
-
xantares authored
-
- 21 Oct, 2013 1 commit
-
-
Pieter Hintjens authored
- removed unnecessary malloc - spaces, not tabs to indent - renamed control states to be more logical - renamed SUSPEND to PAUSE, feels more accurate - fixed indentation, which was off in places
-
- 18 Oct, 2013 3 commits
-
-
Richard Newton authored
-
Laurent Alebarde authored
-
Laurent Alebarde authored
-
- 11 Oct, 2013 1 commit
-
-
Martin Hurton authored
-
- 09 Oct, 2013 1 commit
-
-
Martin Hurton authored
-
- 07 Oct, 2013 2 commits
-
-
-
Brandon Carpenter authored
Abstract socket pathnames must have a NULL character in the first position, but the second character must also be checked to differentiate an abstract name from the empty string. The address length must also indicate the length of the pathname because the kernel uses the entire address as the name, including NULL characters. ZMQ uses NULL-terminated strings for the address, so the abstract address length is the length of the string following the initial NULL byte plus 3; two bytes for the address family and one for the initial NULL character.
-
- 04 Oct, 2013 3 commits
-
-
Volodymyr Korniichuk authored
-
Brandon Carpenter authored
Converts an initial strudel or "at sign" (@) in the Unix socket path to a NULL character ('\0') indicating that the socket uses the abstract namespace instead of the filesystem namespace. For instance, binding a socket to 'ipc://@/tmp/tester' will not create a file associated with the socket whereas binding to 'ipc:///tmp/tester' will create the file /tmp/tester. See issue 567 for more information.
-
Martin Hurton authored
-
- 29 Sep, 2013 2 commits
- 26 Sep, 2013 3 commits
-
-
Pieter Hintjens authored
* Tests dealer-to-router connection 100 times * This was failing in ZMQ v4.0.0 RC1
-
Pieter Hintjens authored
-
Martin Hurton authored
-
- 24 Sep, 2013 1 commit
-
-
Pieter Hintjens authored
* The INITIATE command vouch box is Box[C',S](C->S') instead of Box[C'](C->S), as recommended by https://codesinchaos.wordpress.com/2012/09/09/curvecp-1/, to reduce the risk of client impersonation. * Mirrors the change in libcurve and CurveZMQ specifications.
-
- 20 Sep, 2013 3 commits
-
-
Pieter Hintjens authored
-
Pieter Hintjens authored
-
Pieter Hintjens authored
* ZMQ_REQ_STRICT was negative option (default 1) which goes against the standard, where defaults are zero. I renamed this to ZMQ_REQ_RELAXED. * ZMQ_REQ_REQUEST_IDS felt clumsy and describes the technical solution rather than the problem/requirement. I changed to ZMQ_REQ_CORRELATE which seems more explicit.
-
- 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
-
- 15 Sep, 2013 3 commits
-
-
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
-
Richard Newton authored
-
- 14 Sep, 2013 1 commit
-
-
Richard Newton authored
-
- 12 Sep, 2013 5 commits
-
-
Richard Newton authored
-
Richard Newton authored
-
Richard Newton authored
-
Pieter Hintjens authored
On ZMQ_CURVE_xxxKEY fetches, would return 41 bytes into caller's 40-byte buffer. Now these fetches only return 41 bytes if the caller explicitly provides a 41-byte buffer (i.e. the option size is 41).
-
Richard Newton authored
-
- 10 Sep, 2013 1 commit
-
-
Richard Newton 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.
-