From dev-return-49116-archive-asf-public=cust-asf.ponee.io@phoenix.apache.org Mon Feb 5 21:33:07 2018 Return-Path: X-Original-To: archive-asf-public@eu.ponee.io Delivered-To: archive-asf-public@eu.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by mx-eu-01.ponee.io (Postfix) with ESMTP id 9FBD3180647 for ; Mon, 5 Feb 2018 21:33:07 +0100 (CET) Received: by cust-asf.ponee.io (Postfix) id 8F3DF160C5A; Mon, 5 Feb 2018 20:33:07 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id D852F160C3B for ; Mon, 5 Feb 2018 21:33:06 +0100 (CET) Received: (qmail 12373 invoked by uid 500); 5 Feb 2018 20:33:06 -0000 Mailing-List: contact dev-help@phoenix.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@phoenix.apache.org Delivered-To: mailing list dev@phoenix.apache.org Received: (qmail 12362 invoked by uid 99); 5 Feb 2018 20:33:05 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd4-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 05 Feb 2018 20:33:05 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd4-us-west.apache.org (ASF Mail Server at spamd4-us-west.apache.org) with ESMTP id 7EF6CC0115 for ; Mon, 5 Feb 2018 20:33:05 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd4-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -109.511 X-Spam-Level: X-Spam-Status: No, score=-109.511 tagged_above=-999 required=6.31 tests=[ENV_AND_HDR_SPF_MATCH=-0.5, KAM_ASCII_DIVIDERS=0.8, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_DEF_SPF_WL=-7.5, USER_IN_WHITELIST=-100] autolearn=disabled Received: from mx1-lw-us.apache.org ([10.40.0.8]) by localhost (spamd4-us-west.apache.org [10.40.0.11]) (amavisd-new, port 10024) with ESMTP id INrRhKBI4VJw for ; Mon, 5 Feb 2018 20:33:04 +0000 (UTC) Received: from mailrelay1-us-west.apache.org (mailrelay1-us-west.apache.org [209.188.14.139]) by mx1-lw-us.apache.org (ASF Mail Server at mx1-lw-us.apache.org) with ESMTP id 31FB25FB93 for ; Mon, 5 Feb 2018 20:33:03 +0000 (UTC) Received: from jira-lw-us.apache.org (unknown [207.244.88.139]) by mailrelay1-us-west.apache.org (ASF Mail Server at mailrelay1-us-west.apache.org) with ESMTP id 65EEDE0350 for ; Mon, 5 Feb 2018 20:33:02 +0000 (UTC) Received: from jira-lw-us.apache.org (localhost [127.0.0.1]) by jira-lw-us.apache.org (ASF Mail Server at jira-lw-us.apache.org) with ESMTP id 6C14B240E6 for ; Mon, 5 Feb 2018 20:33:00 +0000 (UTC) Date: Mon, 5 Feb 2018 20:33:00 +0000 (UTC) From: "James Taylor (JIRA)" To: dev@phoenix.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (PHOENIX-4529) Users should only require RX access to SYSTEM.SEQUENCE table MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/PHOENIX-4529?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16352892#comment-16352892 ] James Taylor commented on PHOENIX-4529: --------------------------------------- [~tdsilva] - how about just adding a split policy of MetaDataSplitPolicy if you need to prevent a split for a given tenant+schema? > Users should only require RX access to SYSTEM.SEQUENCE table > ------------------------------------------------------------ > > Key: PHOENIX-4529 > URL: https://issues.apache.org/jira/browse/PHOENIX-4529 > Project: Phoenix > Issue Type: Bug > Reporter: Karan Mehta > Assignee: Thomas D'Silva > Priority: Major > > Currently, users don't need to have Write access to {{SYSTEM.CATALOG}} and other tables, since the code is run on the server side as login user. However for {{SYSTEM.SEQUENCE}}, write permission is still needed. This is a potential security concern, since it allows anyone to modify the sequences created by others. This JIRA is to discuss how we can improve the security of this table. > Potential options include > 1. Usage of HBase Cell Level Permissions (works only with HFile version 3 and above) > 2. AccessControl at Phoenix Layer by addition of user column in the {{SYSTEM.SEQUENCE}} table and use it for access control (Can be error-prone for complex scenarios like sequence sharing) > Please advice. > [~tdsilva] [~jamestaylor] [~apurtell] [~ankit@apache.org] [~elserj] -- This message was sent by Atlassian JIRA (v7.6.3#76005)