1. 08 Aug, 2017 1 commit
    • Simon Giesecke's avatar
      Problem: ZAP status codes != 200 do not result in an appropriate monitor event (#2665) · a6cef4ef
      Simon Giesecke authored
      * Problem: missing test for status code 300, inadequate assertion for status code 500
      
      Solution: add test, change assertion (currently test fails)
      
      * Problem: gcc compiler error deprecated conversion from string constant
      
      Solution: declare variable as const
      
      * Problem: in case of ZAP handler returning a status code other than 200, no appropriate event is emitted
      
      Solution: immediately emit event after receiving reply from ZAP handler
      
      * Problem: endpoint address is not included in zap-reply monitor event
      
      Solution: added functions to retrieve endpoint address in zmq::i_engine and zmq::session_base_t
      removed unused code block in zmq::stream_engine_t::next_handshake_command
      
      * Problem: wrong formatting
      
      Solution: fix formatting
      
      * Problem: test fails because of EPIPE
      
      Solution: add EPIPE/ECONNRESET/ECONNAGAIN handling for more test cases
      a6cef4ef
  2. 01 Jan, 2017 1 commit
    • Vincent Tellier's avatar
      Fixed issue #2227 second part · ffb31dca
      Vincent Tellier authored
       - removed the previously added encryption_error, less changes less bug
       - handshake fail is now signaled when an error happen while the
         mechanism is still hanshaking
      ffb31dca
  3. 30 Dec, 2016 1 commit
    • Vincent Tellier's avatar
      Fixed issue #2227 · b6e9e0c2
      Vincent Tellier authored
      Added two new monitoring events:
       - ZMQ_EVENT_HANDSHAKE_SUCCEED is raised once the encryption handshake succeed
       - ZMQ_EVENT_HANDSHAKE_FAILED is raised when it failed
      Both events are raised on server and client side.
      b6e9e0c2
  4. 15 Dec, 2016 1 commit
  5. 14 May, 2016 1 commit
  6. 28 Jan, 2016 1 commit
  7. 26 Jun, 2015 1 commit
    • Jonathan Reams's avatar
      Fix units and default values for heartbeats options · e9a5bc8d
      Jonathan Reams authored
      Set the ZMQ_HEARTBEAT_TIMEOUT to default to the value of
      ZMQ_HEARTBEAT_IVL if it's not explicitly set.
      Change the units of ZMQ_HEARTBEAT_TTL to milliseconds in the API
      and round down to the nearest decisecond so that all the options
      are using the same units.
      Make the maximum heartbeat TTL match the spec (6553 seconds)
      e9a5bc8d
  8. 24 Jun, 2015 1 commit
  9. 02 Jun, 2015 1 commit
  10. 19 Feb, 2015 1 commit
  11. 18 Feb, 2015 1 commit
  12. 22 Jan, 2015 1 commit
  13. 09 Jan, 2015 1 commit
  14. 22 Jun, 2014 1 commit
    • Martin Hurton's avatar
      Add support for SOCKS proxies · f06ca69a
      Martin Hurton authored
      This is still raw and experimental.
      To connect through a SOCKS proxy, set ZMQ_SOCKS_PROXY socket option on
      socket before issuing a connect call, e.g.:
      
          zmq_setsockopt (s, ZMQ_SOCKS_PROXY,
              "127.0.0.1:22222", strlen ("127.0.0.1:22222"));
          zmq_connect (s, "tcp://127.0.0.1:5555");
      
      Known limitations:
      - only SOCKS version 5 supported
      - authentication not supported
      - new option is still undocumented
      f06ca69a
  15. 17 May, 2014 1 commit
  16. 09 May, 2014 1 commit
  17. 05 May, 2014 1 commit
  18. 02 May, 2014 1 commit
  19. 30 Apr, 2014 1 commit
  20. 12 Jan, 2014 1 commit
  21. 02 Jan, 2014 2 commits
  22. 07 Nov, 2013 1 commit
  23. 09 Oct, 2013 1 commit
  24. 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
  25. 18 Jul, 2013 1 commit
  26. 22 Jun, 2013 1 commit
  27. 21 Jun, 2013 1 commit
  28. 06 Jun, 2013 1 commit
  29. 17 May, 2013 1 commit
    • Pieter Hintjens's avatar
      plain_mechanism now uses options.as_server · f909b9c7
      Pieter Hintjens authored
      - we need to switch to PLAIN according to options.mechanism
      - we need to catch case when both peers are as-server (or neither is)
      - and to use username/password from options, for client
      f909b9c7
  30. 14 May, 2013 2 commits
  31. 28 Apr, 2013 1 commit
  32. 12 Apr, 2013 1 commit
  33. 11 Apr, 2013 1 commit
  34. 12 Mar, 2013 3 commits
    • Pieter Hintjens's avatar
      Code name clean up · 12c7db8c
      Pieter Hintjens authored
      12c7db8c
    • Pieter Hintjens's avatar
      Bumped ZMTP revision to 2 · d826c53b
      Pieter Hintjens authored
      * Starting draft ZMTP/2.1 protocol (revision 2)
      * Basis for adding security to the wire protocol
      * Maintains backward compatibility
      d826c53b
    • Pieter Hintjens's avatar
      Removed corporate advertisements from source file headers · f0f16505
      Pieter Hintjens authored
      Copyrights had become ads for Sustrik's corporate sponsors, going against the original
      agreement to share copyrights with the community (that agreement was: one line stating
      iMatix copyright + one reference to AUTHORS file). The proliferation of corporate ads
      is also unfair to the many individual authors. I've removed ALL corporate title from
      the source files so the copyright statements can now be centralized in AUTHORS and
      source files can be properly updated on an annual basis.
      f0f16505
  35. 01 Feb, 2013 1 commit
  36. 02 Jan, 2013 1 commit