[ 
https://issues.apache.org/jira/browse/KUDU-3787?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18092641#comment-18092641
 ] 

ASF subversion and git services commented on KUDU-3787:
-------------------------------------------------------

Commit 8e54d7be0c5da244871597007fb923f68518bf56 in kudu's branch 
refs/heads/master from Attila Bukor
[ https://gitbox.apache.org/repos/asf?p=kudu.git;h=8e54d7be0 ]

KUDU-3787 Make tls_debug support Kerberos

d4ec371 introduced a new tool to debug TLS connections (diagnose
tls_debug), but unfortunately, it didn't work with Kerberos-enabled
servers, which makes it less practical in real-life environments. With
this change, this tool can be used to debug TLS information on
Kerberos-enabled servers as well (without needing a valid ticket).

It also fixes a bug (which was only present in debug build) that
surfaced while testing skipping authentication where a malformed
negotiation could crash a server.

Change-Id: Ic6c6c9ac1cebeab8cb48bd22aea852c93c0252a4
Reviewed-on: http://gerrit.cloudera.org:8080/24511
Reviewed-by: Marton Greber <[email protected]>
Tested-by: Marton Greber <[email protected]>
Reviewed-by: Alexey Serbin <[email protected]>


> CLI Tool diagnose tls_debug Errors on Kerberos-Enabled Clusters
> ---------------------------------------------------------------
>
>                 Key: KUDU-3787
>                 URL: https://issues.apache.org/jira/browse/KUDU-3787
>             Project: Kudu
>          Issue Type: Bug
>    Affects Versions: 1.19.0
>            Reporter: Jason Fehr
>            Assignee: Attila Bukor
>            Priority: Critical
>
> The kudu diagnose tls_debug tool for reporting TLS configuration of kRPC 
> ports does not work on Kerberos-enabled clusters.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Reply via email to