You are viewing a plain text version of this content. The canonical link for it is here.
Posted to hdfs-dev@hadoop.apache.org by "Tsz-wo Sze (Jira)" <ji...@apache.org> on 2024/07/20 07:18:00 UTC
[jira] [Resolved] (HDFS-17575) SaslDataTransferClient should use SaslParticipant to create messages
[ https://issues.apache.org/jira/browse/HDFS-17575?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Tsz-wo Sze resolved HDFS-17575.
-------------------------------
Fix Version/s: 3.3.7
Resolution: Fixed
The pull request is now merged.
> SaslDataTransferClient should use SaslParticipant to create messages
> --------------------------------------------------------------------
>
> Key: HDFS-17575
> URL: https://issues.apache.org/jira/browse/HDFS-17575
> Project: Hadoop HDFS
> Issue Type: Improvement
> Components: security
> Reporter: Tsz-wo Sze
> Assignee: Tsz-wo Sze
> Priority: Major
> Labels: pull-request-available
> Fix For: 3.3.7
>
>
> Currently, a SaslDataTransferClient may send a message without using its SaslParticipant as below. {code}
> sendSaslMessage(out, new byte[0]);
> {code}
> Instead, it should use its SaslParticipant to create the response.
> {code}
> byte[] localResponse = sasl.evaluateChallengeOrResponse(remoteResponse);
> sendSaslMessage(out, localResponse);
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: hdfs-dev-unsubscribe@hadoop.apache.org
For additional commands, e-mail: hdfs-dev-help@hadoop.apache.org