[jira] [Commented] (HBASE-26666) Address bearer token being sent over wire before RPC encryption is enabled

["Andor Molnar (Jira)" <ji...@apache.org>]

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

Andor Molnar commented on HBASE-26666:
--------------------------------------

I suggest to implement Netty-based TLS encryption for this in Master and RS. Most of the implementation can be copied from the ZooKeeper project where it was implemented recently.

> Address bearer token being sent over wire before RPC encryption is enabled
> --------------------------------------------------------------------------
>
>                 Key: HBASE-26666
>                 URL: https://issues.apache.org/jira/browse/HBASE-26666
>             Project: HBase
>          Issue Type: Sub-task
>            Reporter: Josh Elser
>            Priority: Major
>             Fix For: HBASE-26553
>
>
> Today, HBase must complete the SASL handshake (saslClient.complete()) prior to turning on any RPC encryption (hbase.rpc.protection=privacy, sasl.QOP=auth-conf).
> This is a problem because we have to transmit the bearer token to the server before we can complete the sasl handshake. This would mean that we would insecurely transmit the bearer token (which is equivalent to any other password) which is a bad smell.
> Ideally, if we can solve this problem for the oauth bearer mechanism, we could also apply it to our delegation token interface for digest-md5 (which, I believe, suffers the same problem).



--
This message was sent by Atlassian Jira
(v8.20.1#820001)