[
https://issues.apache.org/jira/browse/HIVE-4887?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13861993#comment-13861993
]
Jason Dere commented on HIVE-4887:
----------------------------------
Hi [~thejas], [~brocknoland], on the subject of UDFs/JARs, for HIVE-6047 I was
proposing that Hive have registered sets of jars which would be referenced by
the UDFs, as opposed to URIs. It would still be similar in that privileges
could be defined so that users can only create UDFs using jars sets they can
access. Let me know if you guys would be ok with that.
> 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: Sub-task
> Components: Authorization, Security
> Reporter: Thejas M Nair
> Original Estimate: 72h
> Remaining Estimate: 72h
>
> 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.5#6160)
