You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "Hudson (JIRA)" <ji...@apache.org> on 2018/03/09 21:04:02 UTC

[jira] [Commented] (HBASE-19634) Add permission check for executeProcedures in AccessController

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

Hudson commented on HBASE-19634:
--------------------------------

Results for branch branch-2
	[build #465 on builds.a.o|https://builds.apache.org/job/HBase%20Nightly/job/branch-2/465/]: (x) *{color:red}-1 overall{color}*
----
details (if available):

(/) {color:green}+1 general checks{color}
-- For more information [see general report|https://builds.apache.org/job/HBase%20Nightly/job/branch-2/465//General_Nightly_Build_Report/]




(x) {color:red}-1 jdk8 hadoop2 checks{color}
-- For more information [see jdk8 (hadoop2) report|https://builds.apache.org/job/HBase%20Nightly/job/branch-2/465//JDK8_Nightly_Build_Report_(Hadoop2)/]


(x) {color:red}-1 jdk8 hadoop3 checks{color}
-- For more information [see jdk8 (hadoop3) report|https://builds.apache.org/job/HBase%20Nightly/job/branch-2/465//JDK8_Nightly_Build_Report_(Hadoop3)/]


(/) {color:green}+1 source release artifact{color}
-- See build output for details.


> Add permission check for executeProcedures in AccessController
> --------------------------------------------------------------
>
>                 Key: HBASE-19634
>                 URL: https://issues.apache.org/jira/browse/HBASE-19634
>             Project: HBase
>          Issue Type: Sub-task
>          Components: proc-v2, Replication
>            Reporter: Duo Zhang
>            Assignee: Duo Zhang
>            Priority: Major
>             Fix For: 3.0.0, 2.1.0
>
>         Attachments: HBASE-19634-HBASE-19397-v1.patch, HBASE-19634-HBASE-19397-v1.patch, HBASE-19634-HBASE-19397-v2.patch, HBASE-19634-HBASE-19397.patch
>
>
> This is important, the actual refresh on RS is trigger by the executeProcedure call and it will pass some information. These information should not be fully trusted since anyone can all this method. We need to make sure that the actual data/state for a replication peer is always loaded from the replication storage, not from the parameter of the executeProcedure call.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)