[
https://issues.apache.org/jira/browse/HADOOP-9421?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13690558#comment-13690558
]
Luke Lu commented on HADOOP-9421:
---------------------------------
bq. Server will not SASL respond to a client until it sends either NEGOTIATE or
INITIATE.
OK, use client NEGOTIATE to replace my empty INITIATE. That's cool.
bq. If the client sends INITIATE, and guesses wrong, the server responds with
NEGOTIATE. Again, the client now has one shot to send a valid INITIATE.
I believe the code could get tricky without a REINITIATE.
bq. Your patch would allow a client to spam INITIATE and keep the socket tied
up indefinitely.
My patch only sends one INITIATE after connection header, it either succeeds or
get a NEGOTIATE to REINITIATE, which doesn't have a transition to NEGOTIATE
again. The code is simple and succinct.
> Convert SASL to use ProtoBuf and add lengths for non-blocking processing
> ------------------------------------------------------------------------
>
> 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: Daryn Sharp
> Priority: Blocker
> Attachments: HADOOP-9421.patch, HADOOP-9421.patch, HADOOP-9421.patch,
> HADOOP-9421.patch, HADOOP-9421.patch, HADOOP-9421.patch, HADOOP-9421.patch,
> HADOOP-9421.patch, HADOOP-9421.patch, HADOOP-9421-v2-demo.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
