hive-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Thejas M Nair (JIRA)" <j...@apache.org>
Subject [jira] [Comment Edited] (HIVE-4887) hive should have an option to disable non sql commands that impose security risk
Date Wed, 20 Nov 2013 03:31:26 GMT

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

Thejas M Nair edited comment on HIVE-4887 at 11/20/13 3:30 AM:
---------------------------------------------------------------

bq. I thought shell commands via ! exec from the CLI or beeline client?
In case of beeline client, ! has special meaning , so you might need to escape that to run
the shell command on HS2. But with o/jdbc in general, if you say "!/bin/hadoop fs ..", that
command will be run on hiveserver2.





was (Author: thejas):
bq. I thought shell commands via ! exec from the CLI or beeline client?
In case of beeline client, "!" has special meaning , so you might need to escape that to run
the shell command on HS2. But with jdbc in general, if you say "!/bin/hadoop fs ..", that
command will be run on hiveserver2.


> hive should have an option to disable non sql commands that impose security risk
> --------------------------------------------------------------------------------
>
>                 Key: HIVE-4887
>                 URL: https://issues.apache.org/jira/browse/HIVE-4887
>             Project: Hive
>          Issue Type: Task
>          Components: Authorization, Security
>            Reporter: Thejas M Nair
>
> Hive's RDBMS style of authorization (using grant/revoke), relies on all data access being
done through hive select queries. But hive also supports running dfs commands, shell commands
(eg "!cat file"), and shell commands through hive streaming.
> This creates problems in securing a hive server using this authorization model. UDF is
another way to write custom code that can compromise security, but you can control that by
restricting access to users to be only through jdbc connection to hive server (2).
> (note that there are other major problems such as this one - HIVE-3271)



--
This message was sent by Atlassian JIRA
(v6.1#6144)

Mime
View raw message