[
https://issues.apache.org/jira/browse/HADOOP-10211?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13902114#comment-13902114
]
Hadoop QA commented on HADOOP-10211:
------------------------------------
{color:green}+1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12629136/HADOOP-10211.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+1 tests included{color}. The patch appears to include 1 new
or modified test files.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 javadoc{color}. There were no new javadoc warning messages.
{color:green}+1 eclipse:eclipse{color}. The patch built with
eclipse:eclipse.
{color:green}+1 findbugs{color}. The patch does not introduce any new
Findbugs (version 1.3.9) warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 core tests{color}. The patch passed unit tests in
hadoop-common-project/hadoop-common.
{color:green}+1 contrib tests{color}. The patch passed contrib unit tests.
Test results:
https://builds.apache.org/job/PreCommit-HADOOP-Build/3581//testReport/
Console output:
https://builds.apache.org/job/PreCommit-HADOOP-Build/3581//console
This message is automatically generated.
> Enable RPC protocol to negotiate SASL-QOP values between clients and servers
> ----------------------------------------------------------------------------
>
> Key: HADOOP-10211
> URL: https://issues.apache.org/jira/browse/HADOOP-10211
> Project: Hadoop Common
> Issue Type: Improvement
> Components: security
> Affects Versions: 2.2.0
> Reporter: Benoy Antony
> Assignee: Benoy Antony
> Attachments: HADOOP-10211.patch, HADOOP-10211.patch,
> HADOOP-10211.patch, HADOOP-10211.patch, HADOOP-10211.patch,
> HADOOP-10221.sample
>
>
> SASL allows different types of protection are referred to as the quality of
> protection (qop). It is negotiated between the client and server during the
> authentication phase of the SASL exchange. Currently hadoop allows specifying
> a single QOP value via _hadoop.rpc.protection_.
> The enhancement enables a user to specify multiple QOP values -
> _authentication_, _integrity_, _privacy_ as a comma separated list via
> _hadoop.rpc.protection_
> The client and server can have different set of values for
> _hadoop.rpc.protection_ and they will negotiate to determine the QOP to be
> used for communication.
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
