1. 02 Feb, 2018 1 commit
  2. 18 Sep, 2017 2 commits
  3. 20 Aug, 2017 1 commit
    • sigiesec's avatar
      Problem: no tests for client-side events for successful handshake and… · bd0675b9
      sigiesec authored
      Problem: no tests for client-side events for successful handshake and authentication failure in handshake
      
      Solution: added tests for CURVE, add emitting of client-side event in curve_client_t; add ZAP code 300/500 tests for all mechanisms; suppress sending an error message for ZAP code 300
      bd0675b9
  4. 18 Aug, 2017 2 commits
  5. 17 Aug, 2017 2 commits
  6. 16 Aug, 2017 4 commits
  7. 15 Aug, 2017 1 commit
    • Simon Giesecke's avatar
      Problem: Possible buffer overruns related to metadata in various mechanisms (#2683) · 4a18f620
      Simon Giesecke authored
      * Problem: no test case with CURVE encryption and large identity
      
      Solution: added test case (currently crashing)
      
      * Problem: possible buffer overflow in mechanism_t::add_property
      
      Solution: add target buffer length parameter and check the buffer is sufficiently large
      
      * Problem: test cases accidentally excluded from build
      
      Solution: remove #if/#endif
      
      * Problem: possible buffer overruns related to metadata at various locations
      
      Solution: allocate buffer large enough for actual metadata, reduce code duplication
      
      * Problem: syntax error related to pointer type conversion
      
      Solution: change argument type of make_command_with_basic_properties to const char *
      
      * Problem: large metadata may cause an assertion in produce_initiate
      
      Solution: Allow metadata of arbitrary size in produce_initiate
      4a18f620
  8. 10 Aug, 2017 1 commit
  9. 04 Aug, 2017 1 commit
  10. 30 Mar, 2017 1 commit
  11. 29 Mar, 2017 2 commits
  12. 14 May, 2016 1 commit
  13. 21 Feb, 2016 1 commit
    • Osiris's avatar
      Problem: Several problems found by Coverity Static Analyzer · b3d5fa63
      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).
      b3d5fa63
  14. 18 Feb, 2016 1 commit
  15. 28 Jan, 2016 1 commit
  16. 02 Jun, 2015 1 commit
  17. 22 Jan, 2015 1 commit
  18. 14 May, 2014 2 commits
  19. 07 May, 2014 1 commit
    • Martin Hurton's avatar
      NULL: Implement ERROR handling · 934560b5
      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.
      934560b5
  20. 06 May, 2014 1 commit
  21. 01 May, 2014 1 commit
  22. 29 Apr, 2014 1 commit
  23. 12 Jan, 2014 1 commit
  24. 02 Jan, 2014 1 commit
  25. 16 Sep, 2013 1 commit
  26. 09 Sep, 2013 2 commits
    • 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
    • Pieter Hintjens's avatar
  27. 04 Sep, 2013 1 commit
    • Pieter Hintjens's avatar
      Updated libzmq to match RFC 23, 24, 25, 26 · 28b0a5fa
      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
      28b0a5fa
  28. 02 Sep, 2013 1 commit
    • 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
  29. 18 Jul, 2013 1 commit
  30. 01 Jul, 2013 1 commit
  31. 28 Jun, 2013 1 commit