Add set of TLS-specific sockets#119
Conversation
Looks good! 👍✅ MERGE
|
Looks good! 👍✅ MERGE
|
Looks good! 👍✅ MERGE
|
Looks good! 👍✅ MERGE
|
Looks good! 👍✅ MERGE
|
8ae9785 to
d6cd21f
Compare
Looks good! 👍✅ MERGE
|
d6cd21f to
6516a35
Compare
Looks good! 👍✅ MERGE
|
6516a35 to
1275fb3
Compare
Looks good! 👍✅ MERGE
|
Looks good! 👍✅ MERGE
|
bbe8fc5 to
5e0b6e3
Compare
Looks good! 👍✅ MERGE
|
5e0b6e3 to
6d26c5e
Compare
Looks good! 👍✅ MERGE
|
6d26c5e to
342f8bb
Compare
pb and tls listener use same sup ignore einval error from peername add tls schema tests error message update tls should be commented out by default Revert change to error message to not reveal reason for auth failure Remove https check from is_authorized set socket to active make tls handshake its own state so that listener is not blocked
Looks good! 👍✅ MERGE
|
Status
2017-01-05- ready for review.Overview
pbandtlslistener use same supervisoreinvalerror frompeername/1Fixes
RIAK-2913Overview of changes:
PB
This PR introduces a
tlssetting in theriak_apienvironment that is a mirror ofpb. When set, Riak will listen for TCP connections on these ports and will always assume SSL/TLS connections on the port(s) configured. TheRpbStartTlsmessage is unnecessary on these ports, and clients that connect to these ports will have to be modified to not send this message an instead send theRpbAuthReqmessage if security is enabled. This means that if security is not enabled, clients can still connect to this port and have encrypted communications without authentication.I modified the code for the legacy pb ports to make the
RpbStartTlsmessage optional. If a client sends this message, TLS will be set up on the socket prior to authentication, preserving backwards compatibility. However, if the client does not sendRpbStartTlsand instead sendsRpbAuthReq, Riak will continue to the authentication phase of the connection establishment. This allows clients to connect to Riak with security enabled but without encryption configured.If a Riak users wishes to enforce encrypted connections, then only
listener.tls...should be configured inriak.conf.HTTP
Removed check for
httpsin theis_authorizedfunction. Auth credentials may be sent over HTTP or HTTPS now.