hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hadoop QA (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-14400) Fix HBase RPC protection documentation
Date Fri, 11 Sep 2015 20:33:46 GMT

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

Hadoop QA commented on HBASE-14400:
-----------------------------------

{color:red}-1 overall{color}.  Here are the results of testing the latest attachment 
  http://issues.apache.org/jira/secure/attachment/12755467/HBASE-14400-branch-0.98.patch
  against 0.98 branch at commit c94d10952fe44f73096027cc9083cee993983940.
  ATTACHMENT ID: 12755467

    {color:green}+1 @author{color}.  The patch does not contain any @author tags.

    {color:green}+1 tests included{color}.  The patch appears to include 4 new or modified
tests.

    {color:green}+1 hadoop versions{color}. The patch compiles with all supported hadoop versions
(2.4.0 2.4.1 2.5.0 2.5.1 2.5.2 2.6.0 2.7.0 2.7.1)

    {color:green}+1 javac{color}.  The applied patch does not increase the total number of
javac compiler warnings.

    {color:green}+1 protoc{color}.  The applied patch does not increase the total number of
protoc compiler warnings.

    {color:green}+1 javadoc{color}.  The javadoc tool did not generate any warning messages.

    {color:green}+1 checkstyle{color}.  The applied patch does not increase the total number
of checkstyle errors

    {color:red}-1 findbugs{color}.  The patch appears to cause Findbugs (version 2.0.3) to
fail.

    {color:green}+1 release audit{color}.  The applied patch does not increase the total number
of release audit warnings.

    {color:green}+1 lineLengths{color}.  The patch does not introduce lines longer than 100

    {color:red}-1 site{color}.  The patch appears to cause mvn post-site goal to fail.

     {color:red}-1 core tests{color}.  The patch failed these unit tests:
     

Test results: https://builds.apache.org/job/PreCommit-HBASE-Build/15568//testReport/
Checkstyle Errors: https://builds.apache.org/job/PreCommit-HBASE-Build/15568//artifact/patchprocess/checkstyle-aggregate.html

  Console output: https://builds.apache.org/job/PreCommit-HBASE-Build/15568//console

This message is automatically generated.

> Fix HBase RPC protection documentation
> --------------------------------------
>
>                 Key: HBASE-14400
>                 URL: https://issues.apache.org/jira/browse/HBASE-14400
>             Project: HBase
>          Issue Type: Bug
>          Components: encryption, rpc, security
>            Reporter: Apekshit Sharma
>            Assignee: Apekshit Sharma
>            Priority: Critical
>             Fix For: 2.0.0, 1.2.1, 1.0.3, 1.1.3
>
>         Attachments: HBASE-14400-branch-0.98.patch, HBASE-14400-branch-1.0.patch, HBASE-14400-branch-1.1.patch,
HBASE-14400-branch-1.2.patch, HBASE-14400-master-v2.patch, HBASE-14400-master.patch
>
>
> HBase configuration 'hbase.rpc.protection' can be set to 'authentication', 'integrity'
or 'privacy'.
> "authentication means authentication only and no integrity or privacy; integrity implies
> authentication and integrity are enabled; and privacy implies all of
> authentication, integrity and privacy are enabled."
> However hbase ref guide incorrectly suggests in some places to set the value to 'auth-conf'
instead of 'privacy'. Setting value to 'auth-conf' doesn't provide rpc encryption which is
what user wants.
> This jira will fix:
> - documentation: change 'auth-conf' references to 'privacy'
> - SaslUtil to support both set of values (privacy/integrity/authentication and auth-conf/auth-int/auth)
to be backward compatible with what was being suggested till now.
> - change 'hbase.thrift.security.qop' to be consistent with other similar configurations
by using same set of values (privacy/integrity/authentication).



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message