- 14 May, 2016 1 commit
-
-
evoskuil authored
-
- 30 Mar, 2016 1 commit
-
-
Pieter Hintjens authored
Solution: use ZMQ_USE_LIBSODIUM to match ZMQ_USE_TWEETNACL
-
- 29 Mar, 2016 1 commit
-
-
Nikolay Edigaryev authored
libsodium calls abort() when /dev/urandom can't be found even if one creates ZeroMQ context before calling chroot()[1]. This happens because crypto gets initialized on handshake, and at that moment the process is already chroot'ed. Solution: initialize cryptographic libraries in ctx randombytes_close() is already there in the destructor. [1] https://download.libsodium.org/doc/usage/index.html
-
- 11 Feb, 2016 2 commits
-
-
Pieter Hintjens authored
- they have no copyright / license statement - they are in some randomish directory structure - they are a mix of postable and non-portable files - they do not conform to conditional compile environment Overall, it makes it rather more work than needed, in build scripts. Solution: clean up tweetnacl sauce. - merged code into single tweetnacl.c and .h - standard copyright header, DJB to AUTHORS - moved into src/ along with all other source files - all system and conditional compilation hidden in these files - thus, they can be compiled and packaged in all cases - ZMQ_USE_TWEETNACL is set when we're using built-in tweetnacl - HAVE_LIBSODIUM is set when we're using external libsodium
-
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.
-
- 28 Jan, 2016 1 commit
-
-
Constantin Rack authored
Solution: update to 2016
-
- 06 Sep, 2015 1 commit
-
-
Constantin Rack authored
-
- 02 Jun, 2015 1 commit
-
-
Pieter Hintjens authored
Of course people still "can" distributed the sources under the LGPLv3. However we provide COPYING.LESSER with additional grants. Solution: specify these grants in the header of each source file.
-
- 22 Jan, 2015 1 commit
-
-
Pieter Hintjens authored
Solution: update for 2015 Fixes #1320
-
- 20 Sep, 2014 1 commit
-
-
Matthew Hawn authored
Solution: ensure message short nonces are strictly increasing and validate them
-
- 15 May, 2014 1 commit
-
-
Martin Hurton authored
-
- 08 May, 2014 1 commit
-
-
Frank authored
-
- 06 May, 2014 1 commit
-
-
Martin Hurton authored
-
- 01 May, 2014 1 commit
-
-
Frank authored
-
- 02 Jan, 2014 1 commit
-
-
Pieter Hintjens authored
-
- 17 Sep, 2013 2 commits
-
-
Pieter Hintjens authored
This reverts commit bfd472f9.
-
Laurent Alebarde authored
-
- 04 Sep, 2013 1 commit
-
-
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
-
- 01 Jul, 2013 1 commit
-
-
Martin Hurton authored
-
- 22 Jun, 2013 2 commits
-
-
Martin Hurton authored
-
Martin Hurton authored
-
- 20 Jun, 2013 1 commit
-
-
Martin Hurton authored
-