You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@hive.apache.org by "Thejas M Nair (JIRA)" <ji...@apache.org> on 2013/12/05 09:23:35 UTC

[jira] [Commented] (HIVE-4887) hive should have an option to disable non sql commands that impose security risk

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

Thejas M Nair commented on HIVE-4887:
-------------------------------------

[~prasadm] Yes, you are right. I went through the code and realized that CliDriver directly processes the shell commands and does not use the CommandProcessor.  I was expecting it to work like dfs and other non-sql statements using CommandProcessor. Thanks for pointing that out!



> 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)