1. 14 May, 2018 1 commit
  2. 02 Feb, 2018 1 commit
  3. 19 Sep, 2017 2 commits
  4. 18 Sep, 2017 1 commit
  5. 07 Sep, 2017 1 commit
  6. 06 Sep, 2017 1 commit
  7. 01 May, 2017 1 commit
    • Luca Boccassi's avatar
      Problem: tests bind to hardcoded TCP ports · 5934919f
      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!
      5934919f
  8. 12 Feb, 2016 1 commit
    • Pieter Hintjens's avatar
      Problem: tests don't build on Windows · 9c0d176d
      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.
      9c0d176d
  9. 06 Feb, 2016 1 commit
  10. 28 Jan, 2016 1 commit
  11. 02 Jun, 2015 1 commit
  12. 07 May, 2015 1 commit
  13. 30 Jan, 2015 1 commit
  14. 22 Jan, 2015 1 commit
  15. 03 Dec, 2014 3 commits
  16. 02 Jan, 2014 1 commit
  17. 18 Sep, 2013 1 commit
  18. 17 Sep, 2013 2 commits
  19. 15 Sep, 2013 1 commit
    • Pieter Hintjens's avatar
      Added z85 codec to ZMQ API · 576e3ca5
      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
      576e3ca5
  20. 12 Sep, 2013 1 commit
  21. 09 Sep, 2013 1 commit
    • Pieter Hintjens's avatar
      Added ZMQ_ZAP_DOMAIN socket option · 6725c464
      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.
      6725c464
  22. 02 Sep, 2013 2 commits
    • Pieter Hintjens's avatar
      Fixed ZAP authentication · fb67e160
      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
      fb67e160
    • Pieter Hintjens's avatar
      Fixed 'make check' failures · fba56120
      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 :-)
      fba56120