[
https://issues.apache.org/jira/browse/HBASE-11434?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14049277#comment-14049277
]
Hadoop QA commented on HBASE-11434:
-----------------------------------
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12653456/HBASE-11434.patch
against trunk revision .
ATTACHMENT ID: 12653456
{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:red}-1 patch{color}. The patch command could not apply the patch.
Console output:
https://builds.apache.org/job/PreCommit-HBASE-Build/9925//console
This message is automatically generated.
> [AccessController] Disallow inbound cells with reserved tags
> ------------------------------------------------------------
>
> Key: HBASE-11434
> URL: https://issues.apache.org/jira/browse/HBASE-11434
> Project: HBase
> Issue Type: Improvement
> Reporter: Andrew Purtell
> Assignee: Andrew Purtell
> Fix For: 0.99.0, 0.98.4
>
> Attachments: HBASE-11434.patch, HBASE-11434.patch, HBASE-11434.patch
>
>
> The AccessController allows users to store cells with ACL tags encoded by the
> client. This isn't a security issue currently, because in order to store the
> cell the user must have a relevant WRITE grant, and the user is allowed to
> specify whatever ACL for the cell they'd like. However it could become a
> correctness problem in the future, if we introduce format sanity checking or
> the like, so let's disallow inbound mutations containing cells with reserved
> tags like the VisibilityController does.
> The check is skipped if the active user is a superuser. First, superusers are
> allowed to do anything. Second, replication (as superuser) must be able to
> store incoming cells with ACL tags.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
