- 21 Feb, 2016 1 commit
-
-
Osiris authored
Solution: The Coverity Static Code Analyzer was used on libzmq code and found many issues with uninitialized member variables, some redefinition of variables hidding previous instances of same variable name and a couple of functions where return values were not checked, even though all other occurrences were checked (e.g. init_size() return).
-
- 18 Feb, 2016 1 commit
-
-
Osiris authored
Solution: Phase I - make precompiled.hpp be first file included in every source file
-
- 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.
-
- 22 Jan, 2015 1 commit
-
-
Pieter Hintjens authored
Solution: update for 2015 Fixes #1320
-
- 14 May, 2014 2 commits
-
-
Martin Hurton authored
-
Martin Hurton authored
-
- 07 May, 2014 1 commit
-
-
Martin Hurton authored
NULL mechanism sends ERROR command rather than READY command when ZAP handler rejects the ZAP request (status code != "200"). The body of ERROR command contains the status code as returned by ZAP handler.
-
- 06 May, 2014 1 commit
-
-
Martin Hurton authored
-
- 01 May, 2014 1 commit
-
-
Martin Hurton authored
-
- 29 Apr, 2014 1 commit
-
-
Pieter Hintjens authored
- additional messages to help people debugging security errors
-
- 12 Jan, 2014 1 commit
-
-
Martin Hurton authored
The get_credential () member function returns credential for the last peer we received message for. The idea is that this function is used to implement user-level API.
-
- 02 Jan, 2014 1 commit
-
-
Pieter Hintjens authored
-
- 16 Sep, 2013 1 commit
-
-
Pieter Hintjens authored
-
- 09 Sep, 2013 2 commits
-
-
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.
-
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 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 :-)
-
- 18 Jul, 2013 1 commit
-
-
Martin Hurton authored
-
- 01 Jul, 2013 1 commit
-
-
Martin Hurton authored
-
- 28 Jun, 2013 1 commit
-
-
Pieter Hintjens authored
RFC23, RFC24, RFC26 now use variable-length command names that end in null octet (valid C strings) instead of fixed-length space padded strings.
-
- 23 Jun, 2013 1 commit
-
-
Martin Hurton authored
-
- 22 Jun, 2013 1 commit
-
-
Martin Hurton authored
-
- 14 May, 2013 1 commit
-
-
Martin Hurton authored
-