1. 26 Dec, 2016 1 commit
  2. 21 Sep, 2016 1 commit
  3. 09 Feb, 2016 4 commits
  4. 08 Feb, 2016 1 commit
  5. 04 Feb, 2016 1 commit
  6. 01 Feb, 2016 3 commits
  7. 08 Dec, 2015 1 commit
    • Ilya Kulakov's avatar
      Add the VMCI transport. · 68b13fbd
      Ilya Kulakov authored
      VMCI transport allows fast communication between the Host
      and a virtual machine, between virtual machines on the same host,
      and within a virtual machine (like IPC).
      
      It requires VMware to be installed on the host and Guest Additions
      to be installed on a guest.
      68b13fbd
  8. 23 Nov, 2015 1 commit
  9. 13 Nov, 2015 2 commits
  10. 08 Nov, 2015 1 commit
  11. 08 Oct, 2015 1 commit
  12. 13 Sep, 2015 1 commit
  13. 11 Sep, 2015 1 commit
  14. 06 Aug, 2015 1 commit
  15. 04 Aug, 2015 2 commits
  16. 08 Jul, 2015 2 commits
  17. 26 Jan, 2015 1 commit
    • Julien Ruffin's avatar
      Added socket option ZMQ_INVERT_MATCHING. · cf2238f8
      Julien Ruffin authored
      ZMQ_INVERT_MATCHING reverses the PUB/SUB prefix matching. The subscription
      list becomes a rejection list. The PUB socket sends messages to all
      connected (X)SUB sockets that do not have any matching subscription.
      
      Whenever the option is used on a PUB/XPUB socket, any connecting SUB
      sockets must also set it or they will reject everything the publisher
      sends them. XSUB sockets are unaffected because they do not filter out
      incoming messages.
      cf2238f8
  18. 09 Jan, 2015 1 commit
  19. 08 Nov, 2014 1 commit
  20. 12 Aug, 2014 1 commit
  21. 20 Jun, 2014 1 commit
  22. 12 May, 2014 1 commit
  23. 09 May, 2014 1 commit
  24. 01 Jan, 2014 2 commits
    • 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
    • Pieter Hintjens's avatar
      Reordered socket options · adf5b45d
      Pieter Hintjens authored
      - put into alphabetical order
      - there was no consistency in previous ordering
      adf5b45d
  25. 06 Dec, 2013 1 commit
    • Brandon Carpenter's avatar
      Add support for extending ZAP request address with IPC peer credentials. · a018ef5e
      Brandon Carpenter authored
      Another take on LIBZMQ-568 to allow filtering IPC connections, this time
      using ZAP.  This change is backward compatible.  If the
      ZMQ_ZAP_IPC_CREDS option is set, the user, group, and process IDs of the
      peer process are appended to the address (separated by colons) of a ZAP
      request; otherwise, nothing changes.  See LIBZMQ-568 and zmq_setsockopt
      documentation for more information.
      a018ef5e
  26. 25 Nov, 2013 1 commit
  27. 09 Oct, 2013 1 commit
  28. 20 Sep, 2013 1 commit
    • Pieter Hintjens's avatar
      Renamed new socket options to be clearer · 5e609be3
      Pieter Hintjens authored
      * ZMQ_REQ_STRICT was negative option (default 1) which goes against
        the standard, where defaults are zero. I renamed this to
        ZMQ_REQ_RELAXED.
      
      * ZMQ_REQ_REQUEST_IDS felt clumsy and describes the technical solution
        rather than the problem/requirement. I changed to ZMQ_REQ_CORRELATE
        which seems more explicit.
      5e609be3
  29. 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
  30. 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
  31. 28 Jun, 2013 1 commit
    • 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