[
https://issues.apache.org/jira/browse/KUDU-3765?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18076518#comment-18076518
]
ASF subversion and git services commented on KUDU-3765:
-------------------------------------------------------
Commit d4ec3717eede2449aa7fc23a3b508068ea6fbf3c in kudu's branch
refs/heads/master from Attila Bukor
[ https://gitbox.apache.org/repos/asf?p=kudu.git;h=d4ec3717e ]
KUDU-3765 Add `diagnose tls_debug` CLI tool
As OpenSSL s_client doesn't support Kudu RPC protocol, it's difficult to
verify that a server is secured properly.
This patch introduces a new CLI tool to assist with this - it simply
prints the negotiated TLS protocol version and the cipher used, along
with whether the extended master secret extension was used in cases of
TLSv1.2 and lower. It also adds this information to the /rpcz endpoint.
It supports disabling TLS using a -disable_tls flag, in which case it
attempts to connect to a server without using TLS.
It also adds support for specifying -tls_min_version, -tls_ciphers
(TLSv1.0 to TLSv1.2), and -tls_ciphersuites (TLSv1.3) for all CLI tools
connecting to a Kudu server.
Change-Id: Ibf90a81d03d1da064a7bc737cf608e2ff97d6ad0
Reviewed-on: http://gerrit.cloudera.org:8080/24222
Tested-by: Kudu Jenkins
Reviewed-by: Alexey Serbin <[email protected]>
> TLS debug CLI tool
> ------------------
>
> Key: KUDU-3765
> URL: https://issues.apache.org/jira/browse/KUDU-3765
> Project: Kudu
> Issue Type: New Feature
> Reporter: Attila Bukor
> Assignee: Attila Bukor
> Priority: Major
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
