Details
Description
Since we send the block tokens unencrypted to the datanode, we currently start the datanode as root using jsvc and get a secure (< 1024) port.
If we have the datanode generate a nonce and send it on the connection and the sends an hmac of the nonce back instead of the block token it won't reveal any secrets. Thus, we wouldn't require a secure port and would not require root or jsvc.
Attachments
Attachments
Issue Links
- breaks
-
HDFS-7382 DataNode in secure mode may throw NullPointerException if client connects before DataNode registers itself with NameNode.
- Closed
- is related to
-
HDFS-6600 fsck -move fails in secured clusters.
- Open
-
HDFS-3749 Disable check for jsvc on windows
- Resolved
-
HDFS-7073 Allow falling back to a non-SASL connection on DataTransferProtocol in several edge cases.
- Closed
-
HDFS-7367 HDFS short-circuit read cannot negotiate shared memory slot and file descriptors when SASL is enabled on DataTransferProtocol.
- Closed
-
HDFS-6859 Allow dfs.data.transfer.protection default to hadoop.rpc.protection
- Resolved
-
HDFS-6606 Optimize HDFS Encrypted Transport performance
- Closed
-
HDFS-7195 Update user doc of secure mode about Datanodes don't require root or jsvc
- Closed
-
HDFS-6858 Allow dfs.data.transfer.saslproperties.resolver.class default to hadoop.security.saslproperties.resolver.class
- Closed
-
HDFS-7386 Replace check "port number < 1024" with shared isPrivilegedPort method
- Closed
- relates to
-
HDFS-3637 Add support for encrypting the DataTransferProtocol
- Closed
-
HADOOP-9671 Improve Hadoop security - Use cases, Threat Model and Problems
- Open