Mailing-List: contact common-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: common-issues@hadoop.apache.org
Date: Wed, 14 Nov 2012 13:22:18 +0000 (UTC)
From: "Hudson (JIRA)" <jira@apache.org>
To: common-issues@hadoop.apache.org
Message-ID: <50269413.113749.1352899338754.JavaMail.jiratomcat@arcas>
In-Reply-To: <415211751.51592.1351704493949.JavaMail.jiratomcat@arcas>
Subject: [jira] [Commented] (HADOOP-8999) SASL negotiation is flawed
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Hudson commented on HADOOP-8999:
--------------------------------

Integrated in Hadoop-Mapreduce-trunk #1257 (See [https://builds.apache.org/job/Hadoop-Mapreduce-trunk/1257/])
    HADOOP-8999. SASL negotiation is flawed (daryn) (Revision 1408837)

     Result = FAILURE
daryn : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1408837
Files : 
* /hadoop/common/trunk/hadoop-common-project/hadoop-common/CHANGES.txt
* /hadoop/common/trunk/hadoop-common-project/hadoop-common/src/main/java/org/apache/hadoop/ipc/Server.java
* /hadoop/common/trunk/hadoop-common-project/hadoop-common/src/main/java/org/apache/hadoop/security/SaslRpcClient.java

                
> SASL negotiation is flawed
> --------------------------
>
>                 Key: HADOOP-8999
>                 URL: https://issues.apache.org/jira/browse/HADOOP-8999
>             Project: Hadoop Common
>          Issue Type: Sub-task
>          Components: ipc
>            Reporter: Daryn Sharp
>            Assignee: Daryn Sharp
>             Fix For: 3.0.0, 2.0.3-alpha
>
>         Attachments: HADOOP-8999.patch
>
>
> The RPC protocol used for SASL negotiation is flawed.  The server's RPC response contains the next SASL challenge token, but a SASL server can return null (I'm done) or a N-many byte challenge.  The server currently will not send a RPC success response to the client if the SASL server returns null, which causes the client to hang until it times out.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira