- 28 May, 2018 1 commit
-
-
Simon Giesecke authored
Solution: extracted constants
-
- 27 May, 2018 1 commit
-
-
Simon Giesecke authored
Problem: inconsistent naming style for private data members, conflicts with naming of local variables and member functions Solution: apply and check _lower_case naming style for private data members
-
- 26 May, 2018 2 commits
-
-
Simon Giesecke authored
Solution: remove else
-
Simon Giesecke authored
Solution: define and apply parameter naming style: lower_case_
-
- 22 May, 2018 1 commit
-
-
Simon Giesecke authored
Solution: add const
-
- 02 Feb, 2018 1 commit
-
-
sigiesec authored
Solution: applied clang-format
-
- 19 Sep, 2017 1 commit
-
-
sigiesec authored
Solution: replace by "routing id"
-
- 18 Sep, 2017 1 commit
-
-
sigiesec authored
mechanisms Solution: uniformly require a ZAP domain to be set to activate ZAP handling, clarify comment on Stonehouse pattern
-
- 07 Sep, 2017 1 commit
-
-
Doron Somech authored
-
- 06 Sep, 2017 1 commit
-
-
sigiesec authored
Solution: replace by "routing id"
-
- 20 Aug, 2017 1 commit
-
-
sigiesec authored
Problem: no tests for client-side events for successful handshake and authentication failure in handshake Solution: added tests for CURVE, add emitting of client-side event in curve_client_t; add ZAP code 300/500 tests for all mechanisms; suppress sending an error message for ZAP code 300
-
- 18 Aug, 2017 3 commits
-
-
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
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
- 16 Aug, 2017 7 commits
-
-
sigiesec authored
Problem: zap_msg_available duplicated between curve_server_t and plain_server_t (with deviating behaviour) Solution: pull up into zap_client_common_handshake_t, along with handle_zap_status_code and error_detail/current_error_detail
-
sigiesec authored
Solution: extract into new intermediate base class zap_client_common_handshake_t
-
sigiesec authored
Solution: extract receive_and_process_zap_reply into zap_client_t and convert zap_client_t into base class of the server mechanism classes
-
sigiesec authored
Solution: Use zap_client_t::send_zap_request
-
sigiesec authored
Solution: Set more flag depending on presence of credentials
-
sigiesec authored
Problem: null_mechanism duplicates zap_client_t::send_zap_request\nSolution: use zap_client_t::send_zap_request
-
sigiesec authored
Solution: created a zap_client_t class, extracted first function send_zap_request from curve_server_t
-