You are viewing a plain text version of this content. The canonical link for it is here.
Posted to hdfs-issues@hadoop.apache.org by "Istvan Toth (Jira)" <ji...@apache.org> on 2024/11/21 09:57:00 UTC
[jira] [Resolved] (HDFS-17669) Do not reqest SASL QOP when using CryptoInput/OutputStream
[ https://issues.apache.org/jira/browse/HDFS-17669?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Istvan Toth resolved HDFS-17669.
--------------------------------
Assignee: Istvan Toth
Resolution: Not A Bug
On closer inspection, Hadoop Encryption DOES use auth-conf for the key exchange.
> Do not reqest SASL QOP when using CryptoInput/OutputStream
> ----------------------------------------------------------
>
> Key: HDFS-17669
> URL: https://issues.apache.org/jira/browse/HDFS-17669
> Project: Hadoop HDFS
> Issue Type: Improvement
> Components: security
> Reporter: Istvan Toth
> Assignee: Istvan Toth
> Priority: Major
> Labels: pull-request-available
>
> CryptoInputStream/CryptioOutputStream does not depend on SASL functionality, yet HDFS requests "auth-conf" QOP when negotatiating it.
> This artifically limits it to be usable only with SASL mechanisms that natively support encryption.
> Hadoop should only set the QOP if it is configured to use native SASL encryption. (i.e. if dfs.encrypt.data.transfer is false)
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: hdfs-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-help@hadoop.apache.org