[
https://issues.apache.org/jira/browse/SENTRY-1209?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15341556#comment-15341556
]
Sravya Tirukkovalur commented on SENTRY-1209:
---------------------------------------------
Reposting my comment from RB
Thanks for the change! The more I think about it, I feel we should be double
careful when making auth model change.
I am trying to think what the user behavior change would be for:
Alter table rename db1.tb1 to db1.tb2: We are essentially dropping db1.tb1 and
creating db1.tb2. So at minimum create and drop on db1 are required. Would
requiring all cause any inflexibility?
Alter table rename db1.tb1 to db2.tb2: At a minimum, user needs drop on db1 and
create on db2. Would requiring all cause any inflexibility?
And also what should our upgrade recommendation be?
> Sentry does not block Hive's cross-schema table renames
> -------------------------------------------------------
>
> Key: SENTRY-1209
> URL: https://issues.apache.org/jira/browse/SENTRY-1209
> Project: Sentry
> Issue Type: Bug
> Components: Core, Hive Binding, Hive Plugin, Sentry
> Affects Versions: 1.5.1
> Environment: CDH 5.5.2
> Reporter: Ruslan Dautkhanov
> Assignee: Colin Ma
> Priority: Critical
> Labels: security
> Attachments: SENTRY-1209.001.patch, SENTRY-1209.002.patch,
> SENTRY-1209.003.patch, SENTRY-1209.004.patch, SENTRY-1209.005.patch
>
>
> User Pete
> has read-write access to schema A
> has read-only access to schema B
> User Pete nevertheless was able to rename/move Hive table
> from schema A to schema B (where he has read-only access):
> {quote}
> use A;
> alter table table_a rename to B.table_a;
> {quote}
> Hive allows to use rename table syntax to move tables across schemas, not
> just rename.
> Sentry does not check security boundaries in this case.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
