problem: browser cannot communicate with zeromq directly

Use libsodium based allocator

Solution: properly set defines from test_security_curve

Solution: implement ZWS 2.0 which websocket transport for zeromq

Solution: Use secure_allocator_t for plaintext secrets

Solution: Added secure_allocator_t based on libsodium's memory management functions when available

Solution: Fixed C++ standard in clang-format config

Problem: unused parameter in benchmark function

Solution: remove it

Problem: use of malloc is error-prone

Static analysis warnings

Solution: use std::vector instead, simplify control-flow

Solution: set -e in ci_build.sh like in other scripts

Solution: don't write it

Solution: add them

problem: wrong api_key for bintray

Solution: update it

Free memory when curve_client sends invalid ready message.

Problem: Missing ZeroMQ_INCLUDE_DIR when only static lib is built

Problem: 4.3.2 is out, need new version

Solution: bump to 4.3.3

CVE-2019-13132

Solution: bump them

Solution: list new features and bug fixes

Solution: fix them

Solution: create buffers large enough to contain arbitrary metadata

Request handling leaked memory.  Depending on the application's use o…

Add relicense agreement from Lourens Naudé

Problem: no security policy

Solution: add SECURITY.md with supported branches and maintainers public keys for private communications

Problem: code doesn't follow libzmq naming conventions

Solution: rename types/variables that are inconsistent

Clarify documentation for zmq_unbind/disconnect and new batch options

Solution: restore separate zmq_unbind documentation, adding a note that the implementation
might be shared but the semantics are different and should not be mixed.
This avoids tying the API to the implementation details which might change for some
engines.