[
https://issues.apache.org/jira/browse/HADOOP-9421?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13690513#comment-13690513
]
Daryn Sharp commented on HADOOP-9421:
-------------------------------------
It's really not worth debating anymore, but if the client decided to guess and
blast a INITIATE, it could simply set a ignoreNegotiate boolean. A server
upgrade is exactly one of the reasons the client shouldn't be guessing.
During authentication the socket reader isn't "fair". As long as there is
pending data from the client, it will keep reading until it gets the first RPC.
It's not a problem today because the client is forced along a path that either
ends in the connection being aborted, or the reading of an RPC. Your patch
would allow a client to spam INITIATE and keep the socket tied up indefinitely.
New patch arriving shortly...
> 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-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
