hadoop-common-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Daryn Sharp (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HADOOP-9421) Add full length to SASL response to allow non-blocking readers
Date Thu, 11 Apr 2013 22:05:18 GMT

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

Daryn Sharp commented on HADOOP-9421:

A comment on HADOOP-9034 indicated it is being addressed on this jira, but this appears a
bit different in scope - primarily converting the sasl exchange to protobufs.

The SASL authentication exchange needs to be overhauled but this patch simply migrates the
existing flawed behavior into protobufs.  We need more than success and error sasl states
and we need a way for the client and server to negotiate the SASL mechanism(s) to be tried.
 The "switch to simple" needs to be completely replaced with a more general interface.

I've thought about this a lot, but generally in terms of small "compatible" tweaks that smash
a square peg into a round hole.  If the RPC version is revving, now is the perfect time to
fix the authentication exchange.  I'll formulate my thoughts tonight and summarize in the
morning.  I'm very excited!
> Add full length to SASL response to allow non-blocking readers
> --------------------------------------------------------------
>                 Key: HADOOP-9421
>                 URL: https://issues.apache.org/jira/browse/HADOOP-9421
>             Project: Hadoop Common
>          Issue Type: Sub-task
>    Affects Versions: 2.0.3-alpha
>            Reporter: Sanjay Radia
>            Assignee: Junping Du
>         Attachments: HADOOP-9421.patch

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

View raw message