[
https://issues.apache.org/jira/browse/HADOOP-3536?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12607333#action_12607333
]
aw edited comment on HADOOP-3536 at 6/23/08 11:34 AM:
--------------------------------------------------------------------
/thinking out loud
i wonder if this is the correct long term approach for if/when hadoop gets a
real authentication api. i know--it doesn't exist yet, but...
i guess i'm concerned about adding api's that might be deprecated sooner rather
than later.
was (Author: aw):
/thinking out load
i wonder if this is the correct long term approach for if/when hadoop gets a
real authentication api. i know--it doesn't exist yet, but...
i guess i'm concerned about adding api's that might be deprecated sooner rather
than later.
> 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
> Attachments: getlogininfo.c
>
>
> 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.
