[
https://issues.apache.org/jira/browse/SENTRY-960?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15023714#comment-15023714
]
Lenni Kuff commented on SENTRY-960:
-----------------------------------
Hi [~sravya], after more consideration I agree with the fact that Hive
whitelists are too restrictive. We should go with your blacklist approach until
Hive is fixed. +1 on that patch. Thanks for the thourough investigation.
> Sentry no longer enforces it's whitelist
> ----------------------------------------
>
> Key: SENTRY-960
> URL: https://issues.apache.org/jira/browse/SENTRY-960
> Project: Sentry
> Issue Type: Bug
> Components: Sentry
> Reporter: Ryan P
> Assignee: Sravya Tirukkovalur
> Attachments: SENTRY-960.10.patch, SENTRY-960.11.patch,
> SENTRY-960.12.patch, SENTRY-960.2.patch, SENTRY-960.3.patch,
> SENTRY-960.4.patch, SENTRY-960.4.patch, SENTRY-960.5.patch,
> SENTRY-960.6.patch, SENTRY-960.7.patch, SENTRY-960.8.patch,
> SENTRY-960.9.patch, SENTRY-960.patch
>
>
> HiveSemanticAnalyzerHookContext no longer includes built-in functions as an
> input to it's Read Entities. This change hides built in functions from
> HiveAuthzBindingHook which is a huge security hole.
> Failing to enforce the whitelist will allow users to execute such functions
> as REFLECT and JAVA_METHOD.
> https://cwiki.apache.org/confluence/display/Hive/ReflectUDF
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
