[
https://issues.apache.org/jira/browse/HDFS-17669?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17899734#comment-17899734
]
ASF GitHub Bot commented on HDFS-17669:
---------------------------------------
stoty opened a new pull request, #7175:
URL: https://github.com/apache/hadoop/pull/7175
### Description of PR
Do not reqest SASL QOP when using CryptoInput/OutputStream
### How was this patch tested?
It wasn't tested yet, this is a draft
### For code changes:
- [x] Does the title or this PR starts with the corresponding JIRA issue id
(e.g. 'HADOOP-17799. Your PR title ...')?
- [ ] Object storage: have the integration tests been executed and the
endpoint declared according to the connector-specific documentation?
- [ ] If adding new dependencies to the code, are these dependencies
licensed in a way that is compatible for inclusion under [ASF
2.0](http://www.apache.org/legal/resolved.html#category-a)?
- [ ] If applicable, have you updated the `LICENSE`, `LICENSE-binary`,
`NOTICE-binary` files?
> 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
> Priority: Major
>
> 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-unsubscr...@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
