1. 31 Jan, 2014 1 commit
  2. 02 Jan, 2014 1 commit
  3. 01 Jan, 2014 1 commit
    • Pieter Hintjens's avatar
      Removed ZMQ_ZAP_IPC_CREDS option · 5bf96f64
      Pieter Hintjens authored
      - This seems redundant; is there a use case for NOT providing
        the IPC credentials to the ZAP authenticator?
      
      - More, why is IPC authentication done via libzmq instead of ZAP?
        Is it because we're missing the transport type on the ZAP request?
      5bf96f64
  4. 06 Dec, 2013 2 commits
  5. 04 Dec, 2013 1 commit
  6. 25 Nov, 2013 1 commit
  7. 26 Sep, 2013 1 commit
  8. 17 Sep, 2013 4 commits
  9. 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
  10. 12 Sep, 2013 1 commit
    • Pieter Hintjens's avatar
      Fixed overwrite in zmq_getsockopt · 345bf146
      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).
      345bf146
  11. 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
  12. 18 Aug, 2013 1 commit
    • Ian Barber's avatar
      Remove delay options · 531d3ebc
      Ian Barber authored
      These were exposed to users, but have subsequently been removed as
      sockopts. They are currently only being used by ZAP, so I've moved it to
      a simpl function call (actually it's only used in one case even in that,
      so there may be a further simplification possible there).
      531d3ebc
  13. 17 Aug, 2013 1 commit
  14. 03 Jul, 2013 1 commit
  15. 29 Jun, 2013 1 commit
  16. 28 Jun, 2013 2 commits
    • Pieter Hintjens's avatar
      Added Z85 support · 70417701
      Pieter Hintjens authored
      The use of binary for CURVE keys is painful; you cannot easily copy
      these in e.g. email, or use them directly in source code. There are
      various encoding possibilities. Base16 and Base64 are not optimal.
      Ascii85 is not safe for source (it generates quotes and escapes).
      
      So, I've designed a new Base85 encoding, Z85, which is safe to use
      in code and elsewhere, and I've modified libzmq to use this where
      it also uses binary keys (in get/setsockopt).
      
      Very simply, if you use a 32-byte value, it's Base256 (binary),
      and if you use a 40-byte value, it's Base85 (Z85).
      
      I've put the Z85 codec into z85_codec.hpp, it's not elegant C++
      but it is minimal and it works. Feel free to rewrap as a real class
      if this annoys you.
      70417701
    • Pieter Hintjens's avatar
  17. 22 Jun, 2013 2 commits
  18. 20 Jun, 2013 1 commit
    • Pieter Hintjens's avatar
      Added options for CURVE security · d9bb1672
      Pieter Hintjens authored
      - ZMQ_CURVE_PUBLICKEY for clients and servers
      - ZMQ_CURVE_SECRETKEY for clients
      - ZMQ_CURVE_SERVERKEY for clients
      - ZMQ_CURVE_SERVER for servers
      - added tools/curve_keygen.c as example
      - updated man pages
      d9bb1672
  19. 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
  20. 15 May, 2013 1 commit
    • Pieter Hintjens's avatar
      Added configuration for PLAIN security · e1f797b0
      Pieter Hintjens authored
      * ZMQ_PLAIN_SERVER, ZMQ_PLAIN_USERNAME, ZMQ_PLAIN_PASSWORD options
      * Man page changes to zmq_setsockopt and zmq_getsockopt
      * Man pages for ZMQ_NULL, ZMQ_PLAIN, and ZMQ_CURVE
      * Test program test_security
      e1f797b0
  21. 12 Mar, 2013 2 commits
  22. 20 Feb, 2013 1 commit
  23. 19 Feb, 2013 1 commit
  24. 31 Jan, 2013 1 commit
  25. 30 Jan, 2013 1 commit
  26. 02 Jan, 2013 2 commits
  27. 09 Nov, 2012 1 commit
  28. 29 Oct, 2012 1 commit
    • Hardeep's avatar
      Added support for non-zmq tcp client connections to router socket. · 83387b40
      Hardeep authored
          - Created a new option ZMQ_ROUTER_RAW_SOCK
          - Added new raw_encoder and raw_decoder to receive and send messages in raw form to remote client
          - Added test case file tests/test_raw_sock.cpp
      
          o To create a raw router sock set the ZMQ_ROUTER_RAW_SOCK option
          o ZMQ_MSGMORE flag is ignored for non-id messages
          o To terminate a remote connection send id message followed by zero length data message
      83387b40
  29. 11 Aug, 2012 1 commit
  30. 12 Jun, 2012 2 commits
    • Ian Barber's avatar
      Allow blocking while connect() is completing · e5904e63
      Ian Barber authored
      This patch, salvaged from a trainwreck accidental merge earlier, adds a
      new sockopt, ZMQ_DELAY_ATTACH_ON_CONNECT which prevents a end point
      being available to push messages to until it has fully connected, making
      connect work more like bind. This also applies to reconnecting sockets,
      which may cause message loss of in-queue messages, so it is sensible to
      use this in conjunction with a low HWM and potentially an alternative
      acknowledgement path.
      
      Notes on most of the individual commits can be found the repository log.
      e5904e63
    • Ian Barber's avatar
      Revert "After speaking with Ben Gray and the discussion on the mailing list,… · 95cbad38
      Ian Barber authored
      Revert "After speaking with Ben Gray and the discussion on the mailing list, this is an attempt to create a sockopt to allow connecting pipes to not immediately be available for traffic. The problem is in a PUSH to many PULL situation, where there is a connect to a PULL which is not there. This connect will immediately create a pipe (unlike bind), and traffic will be load balanced to that pipe. This means if there is a persistently unavailable end point then the traffic will queue until HWM is hit, and older messages will be lost."
      
      This reverts commit fe3fb419.
      95cbad38
  31. 01 Jun, 2012 1 commit
    • Ian Barber's avatar
      After speaking with Ben Gray and the discussion on the mailing list, this is an… · fe3fb419
      Ian Barber authored
      After speaking with Ben Gray and the discussion on the mailing list, this is an attempt to create a sockopt to allow connecting pipes to not immediately be available for traffic. The problem is in a PUSH to many PULL situation, where there is a connect to a PULL which is not there. This connect will immediately create a pipe (unlike bind), and traffic will be load balanced to that pipe. This means if there is a persistently unavailable end point then the traffic will queue until HWM is hit, and older messages will be lost.
      
      This patch adds a sockopt ZMQ_DELAY_ATTACH_ON_CONNECT, which if set to 1 will attempt to preempt this behavior. It does this by extending the use of the session_base to include in the outbound as well as the inbound pipe, and only associates the pipe with the socket once it receives the connected callback via a process_attach message. This works, and a test has been added to show so, but may introduce unexpected complications. The shutdown logic in this class has become marginally more awkward because of this, requiring the session to serve as the sink for both pipes if shutdown occurs with a still-connecting pipe in place. It is also possible there could be issues around flushing the messages, but as I could not directly think how to create such an issue I have not written any code with regards to that.
      
      The documentation has been updated to reflect the change, but please do check over the code and test and review.
      fe3fb419