1. 22 Aug, 2018 1 commit
  2. 02 Feb, 2018 1 commit
  3. 19 Jan, 2017 1 commit
  4. 11 Feb, 2016 1 commit
    • Pieter Hintjens's avatar
      Problem: use of libsodium vs. tweetnacl is confused · b49a6041
      Pieter Hintjens authored
      It's unclear which we need and in the source code, conditional code
      treats tweetnacl as a subclass of libsodium, which is inaccurate.
      
      Solution: redesign the configure/cmake API for this:
      
      * tweetnacl is present by default and cannot be enabled
      * libsodium can be enabled using --with-libsodium, which replaces
        the built-in tweetnacl
      * CURVE encryption can be disabled entirely using --enable-curve=no
      
      The macros we define in platform.hpp are:
      
          ZMQ_HAVE_CURVE    1        //  When CURVE is enabled
          HAVE_LIBSODIUM    1        //  When we are using libsodium
          HAVE_TWEETNACL    1        //  When we're using tweetnacl (default)
      
      As of this patch, the default build of libzmq always has CURVE
      security, and always uses tweetnacl.
      b49a6041
  5. 28 Jan, 2016 1 commit
  6. 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
  7. 02 Jun, 2015 1 commit
  8. 22 Jan, 2015 1 commit
  9. 19 Jun, 2014 1 commit
  10. 18 Jun, 2014 1 commit
    • Pieter Hintjens's avatar
      Problem: need way to probe library capabilities · f11d673b
      Pieter Hintjens authored
      As libzmq is compiled with optional transports and security mechanisms,
      there is no clean way for applications to determine what capabilities
      are actually available in a given libzmq instance.
      
      Solution: provide an API specifically for capability reporting. The
      zmq_has () method is meant to be open ended. It accepts a string so
      that we can add arbitrary capabilities without breaking existing
      applications.
      
      zmq.h also defines ZMQ_HAS_CAPABILITIES when this method is provided.
      f11d673b
  11. 30 Apr, 2014 1 commit
  12. 02 Jan, 2014 1 commit
  13. 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
  14. 17 Aug, 2013 1 commit
  15. 12 Mar, 2013 1 commit
  16. 31 Jan, 2013 2 commits
  17. 06 Sep, 2012 1 commit
    • Arthur O'Dwyer's avatar
      Add "#undef NDEBUG" to all tests. · cf20932d
      Arthur O'Dwyer authored
      This change makes sure that even if the tests are built in a
      "release" configuration (with optimizations and NDEBUG turned on),
      the assertions won't get compiled out of the tests themselves.
      
      The C standard guarantees that the most recent inclusion of
      <assert.h> is the one that counts, so it's important that the
      "#undef NDEBUG/#include <assert.h>" come as the last thing in
      the block of header files.
      
      "testutil.hpp" includes <assert.h>, so I've left <assert.h> out
      of any test that #includes "testutil.hpp", just for the sake of
      brevity.
      cf20932d
  18. 27 Aug, 2012 1 commit
  19. 01 Nov, 2011 2 commits
  20. 31 Oct, 2011 1 commit
  21. 03 Jul, 2011 1 commit
  22. 24 Mar, 2011 1 commit
  23. 02 Mar, 2011 1 commit
  24. 30 Oct, 2010 1 commit
  25. 28 Aug, 2010 1 commit
  26. 27 Aug, 2010 2 commits
  27. 13 Feb, 2010 1 commit
  28. 05 Jan, 2010 1 commit
  29. 10 Dec, 2009 1 commit
  30. 03 Nov, 2009 1 commit
  31. 05 Oct, 2009 1 commit
  32. 03 Aug, 2009 1 commit
  33. 29 Jul, 2009 1 commit