[
https://issues.apache.org/jira/browse/HADOOP-3536?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12604297#action_12604297
]
Doug Cutting commented on HADOOP-3536:
--------------------------------------
> it would be better to run fuse-dfr as some privileged user, and use Hadoop
> API calls determine whether the current user was privileged
This sounds potentially dangerous and expensive. If the fuse code has the
username making the request, it can set it in the configuration passed to
FileSystem.get(URI, Configuration).
> Support permissions in fuse-dfs
> -------------------------------
>
> Key: HADOOP-3536
> URL: https://issues.apache.org/jira/browse/HADOOP-3536
> Project: Hadoop Core
> Issue Type: New Feature
> Components: contrib/fuse-dfs
> Reporter: Craig Macdonald
>
> Currently permissions are unsupported by fuse-dfs.
> This manifests itself as two issues:
> * Users accessing a fuse-dfs mount do so as the user running fuse_dfs
> executable. In this case, it would be better to run fuse-dfr as some
> privileged user, and use Hadoop API calls determine whether the current user
> was privileged enough to perform the action.
> * Users cannot view/change permissions on the mounted volume. See
> HADOOP-3264
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
