- 19 Aug, 2017 18 commits
-
-
Constantin Rack authored
Problems: GSSAPI builds broken with picky compilers, Debian/RPM packages do not use GSSAPI, no CI jobs that test GSSAPI
-
Luca Boccassi authored
Solution: enable option and install build-dependency for the jobs that already install packages only, to minimise marginal cost in term of runtime
-
Luca Boccassi authored
Solution: enable option and install build-dependency for the jobs that already install packages only, to minimise marginal cost in term of runtime
-
Luca Boccassi authored
Solution: fix it
-
Luca Boccassi authored
Solution: add build-dependency and configure option
-
Luca Boccassi authored
Solution: cast from void* to uint8_t* to match new definition
-
Luca Boccassi authored
Solution: initialise session and peer_address
-
Luca Boccassi authored
Solution: pass the session as well as the options
-
Luca Boccassi authored
Solution: remove it from the gssapi_mechanism_base initialiser
-
Luca Boccassi authored
Solution: remove local unused zap_client variable
-
Luca Boccassi authored
Solution: move them together with the other DRAFT socket options, and change value of DRAFT ZMQ_BINDTODEVICE from 90 to 92 to avoid clash
-
Luca Boccassi authored
Solution: include mechanism_base.hpp instead of mechanism.hpp
-
Luca Boccassi authored
Solution: call make_command_with_basic_properties
-
Doron Somech authored
Problems: free of stack variable, TODO left to evaluate
-
Luca Boccassi authored
Solution: add missing target_link_libraries Fixes #2701
-
Luca Boccassi authored
Solution: use LIBZMQ_UNUSED where necessary
-
Luca Boccassi authored
Solution: add it to CMake's platform.hpp.in
-
Luca Boccassi authored
Solution: as discussed, remove the deprecation notices, as many users expressed the need for multi-part support. Fixes #2699
-
- 18 Aug, 2017 19 commits
-
-
Luca Boccassi authored
Solution: monitor new events only if DRAFT APIs are enabled, and convert to new event types. Same for DRAFT socket options.
-
Luca Boccassi authored
Solution: remove the second one to fix build failure
-
Luca Boccassi authored
Solution: use it before falling back to headers checks
-
Luca Boccassi authored
Solution: remove it. Looking at the code: https://github.com/krb5/krb5/blob/master/src/lib/gssapi/mechglue/g_unseal.c#L55 gss_unwrap as the very first thing checks that plaintext is not a null pointer, which in our case it's true given it's on the stack, and then initialises its members to 0 length and null ptr. https://github.com/krb5/krb5/blob/master/src/lib/gssapi/mechglue/g_rel_buffer.c#L36 So it should be safe to release it in all cases, and the release API seems to check again if it's not a null pointer and then if the members are 0 length and null pointer it's a no-op.
-
Luca Boccassi authored
Solution: free wrapper.value instead of wrapper.
-
Doron Somech authored
Problem: missing files from VS2008 solution
-
Luca Boccassi authored
Problem: gssapi_mechanism_base_t aborts the application when it receives a message it cannot decode
-
Luca Boccassi authored
Solution: generate list of sources and headers with: ls -1 src/*cpp | sort | sed 's|src/\(.*\)| <File RelativePath="..\\..\\..\\..\\src\\\1" />|g' ls -1 src/*hpp | sort | sed 's|src/\(.*\)| <File RelativePath="..\\..\\..\\..\\src\\\1" />|g' and add them.
-
sigiesec authored
Solution: emit an ZMQ_EVENT_HANDSHAKE_FAILED_PROTOCOL event instead of using zmq_assert
-
Luca Boccassi authored
Problem: Values in ZMQ_EVENT_HANDSHAKE_FAILED_* are not helpful
-
sigiesec authored
Solution: extracted common base class curve_mechanism_base_t
-
sigiesec authored
Solution: emit appropriate events
-
sigiesec authored
Solution: emit events at appropriate places
-
sigiesec authored
Solution: use check_basic_command_structure in curve_client_t::decode, also prepare other client mechanisms to use that method by rearranging inheritance hierarchy
-
sigiesec authored
state of ZMQ_EVENT_HANDSHAKE_FAILED_* events Solution: update documentation
-
sigiesec authored
Solution: add handshake failure events to curve_client_t
-
sigiesec authored
Solution: emit socket monitor events for NULL protocol errors (like CURVE)
-
sigiesec authored
Solution: emit socket monitor events for PLAIN protocol errors (like CURVE)
-
sigiesec authored
Solution: redesign ZMQ_HANDSHAKE_FAILED_* events, introduce new class of ZMQ_HANDSHAKE_FAILED_AUTH events
-
- 17 Aug, 2017 3 commits
-
-
Constantin Rack authored
Problem: coverage CI job does not print test errors
-
Luca Boccassi authored
Solution: run make check with VERBOSE=1
-
Luca Boccassi authored
specify that groups shall be UTF8
-