FAQ
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.

Search Discussions

  • Doug Cutting (JIRA) at Jun 11, 2008 at 6:23 pm
    [ 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.
  • Craig Macdonald (JIRA) at Jun 11, 2008 at 6:27 pm
    [ https://issues.apache.org/jira/browse/HADOOP-3536?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12604299#action_12604299 ]

    Craig Macdonald commented on HADOOP-3536:
    -----------------------------------------

    Doug, so your suggesting essentially a FileSystem object open for each user accessing the DFS?

    The alternative is having mounts for every user (which is still in the spirit of fuse).

    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.
  • Doug Cutting (JIRA) at Jun 11, 2008 at 6:39 pm
    [ https://issues.apache.org/jira/browse/HADOOP-3536?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12604302#action_12604302 ]

    Doug Cutting commented on HADOOP-3536:
    --------------------------------------
    Doug, so your suggesting essentially a FileSystem object open for each user accessing the DFS?
    Yes. FileSystem.get() caches instances based on username, and the RPC system cache's connections based on username. So applications should not need to do more than be sure they pass a Configuration that contains the user's credentials. Currently credentials are set/get in a Configuration only by UnixUserGroupInformation.java.
    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.
  • Craig Macdonald (JIRA) at Jun 23, 2008 at 6:19 pm
    [ https://issues.apache.org/jira/browse/HADOOP-3536?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12607327#action_12607327 ]

    Craig Macdonald commented on HADOOP-3536:
    -----------------------------------------

    Ok, this would require some minor changes in libhdfs API.

    Currently, the connection API is:
    [noformat]
    hdfsFS hdfsConnect(const char* host, tPort port);
    [noformat]

    I suggest adding one or two additional API calls, to allow connection as a given user:
    [noformat]
    /**
    * hdfsConnect - Connect to a hdfs file system as the specified user, and all
    * of his/her groups
    */
    hdfsFS hdfsConnect(const char* host, tPort port, uid_t uid);

    /**
    * hdfsConnect - Connect to a hdfs file system as the specified user, and only the specified group
    */
    hdfsFS hdfsConnect(const char* host, tPort port, uid_t uid, gid_t gid);

    [noformat]

    This would require libhdfs to achieve two tasks:
    * For a given uid, determine the username and all his/her groups (names), and use these to access a FileSystem object
    * For a given uid, determine the username and the group names

    Code to achieve this attached.


    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.
  • Craig Macdonald (JIRA) at Jun 23, 2008 at 6:23 pm
    [ https://issues.apache.org/jira/browse/HADOOP-3536?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

    Craig Macdonald updated HADOOP-3536:
    ------------------------------------

    Attachment: getlogininfo.c

    Code to determine:
    * uid -> username
    * uid -> username,all groupnames

    This code could be used to set the hadoop.job.ugi property to obtain the correct FileSystem object for each user accessing the DFS.
    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.
  • Craig Macdonald (JIRA) at Jun 23, 2008 at 6:29 pm
    [ https://issues.apache.org/jira/browse/HADOOP-3536?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12607327#action_12607327 ]

    craigm edited comment on HADOOP-3536 at 6/23/08 11:27 AM:
    -------------------------------------------------------------------

    Ok, this would require some minor changes in libhdfs API.

    Currently, the connection API is:
    {noformat}
    hdfsFS hdfsConnect(const char* host, tPort port);
    {noformat}

    I suggest adding one or two additional API calls, to allow connection as a given user:
    {noformat}
    /**
    * hdfsConnect - Connect to a hdfs file system as the specified user, and all
    * of his/her groups
    */
    hdfsFS hdfsConnect(const char* host, tPort port, uid_t uid);

    /**
    * hdfsConnect - Connect to a hdfs file system as the specified user, and only the specified group
    */
    hdfsFS hdfsConnect(const char* host, tPort port, uid_t uid, gid_t gid);

    {noformat}

    This would require libhdfs to achieve two tasks:
    * For a given uid, determine the username and all his/her groups (names), and use these to access a FileSystem object
    * For a given uid, determine the username and the group names, and use these to access a FileSystem object

    Code to achieve this attached.



    was (Author: craigm):
    Ok, this would require some minor changes in libhdfs API.

    Currently, the connection API is:
    [noformat]
    hdfsFS hdfsConnect(const char* host, tPort port);
    [noformat]

    I suggest adding one or two additional API calls, to allow connection as a given user:
    [noformat]
    /**
    * hdfsConnect - Connect to a hdfs file system as the specified user, and all
    * of his/her groups
    */
    hdfsFS hdfsConnect(const char* host, tPort port, uid_t uid);

    /**
    * hdfsConnect - Connect to a hdfs file system as the specified user, and only the specified group
    */
    hdfsFS hdfsConnect(const char* host, tPort port, uid_t uid, gid_t gid);

    [noformat]

    This would require libhdfs to achieve two tasks:
    * For a given uid, determine the username and all his/her groups (names), and use these to access a FileSystem object
    * For a given uid, determine the username and the group names

    Code to achieve this attached.


    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.
  • Allen Wittenauer (JIRA) at Jun 23, 2008 at 6:33 pm
    [ https://issues.apache.org/jira/browse/HADOOP-3536?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12607333#action_12607333 ]

    Allen Wittenauer commented on HADOOP-3536:
    ------------------------------------------


    /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.
  • Allen Wittenauer (JIRA) at Jun 23, 2008 at 6:37 pm
    [ 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.
  • Craig Macdonald (JIRA) at Jun 23, 2008 at 6:47 pm
    [ https://issues.apache.org/jira/browse/HADOOP-3536?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12607340#action_12607340 ]

    Craig Macdonald commented on HADOOP-3536:
    -----------------------------------------

    In all cases, sometimes a process will need to have an 'asuser' privilege - which mean it needs to access the DFS as other arbitrary users. Perhaps the libhdfs API would not need to change in the future, but the implementation to support the permissions may change.

    The crucial point is how does Hadoop tell if the current user has the 'asuser' privilege.

    Also, I'm using uid_t/gid_t to designate a user, (char* username, char** groupnames) would be OK by me as well.

    C
    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.
  • Pete Wyckoff (JIRA) at Jul 10, 2008 at 11:58 pm
    [ https://issues.apache.org/jira/browse/HADOOP-3536?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12612700#action_12612700 ]

    Pete Wyckoff commented on HADOOP-3536:
    --------------------------------------

    IS this issue really "respecting" permissions in the fuse module or also the ability to set permissions? Maybe should be divided in 2 since it seems the underlying APIs needed in libhdfs may end up in 2 JIRAs themselves??

    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.
  • Craig Macdonald (JIRA) at Jul 13, 2008 at 3:56 pm
    [ https://issues.apache.org/jira/browse/HADOOP-3536?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12613170#action_12613170 ]

    Craig Macdonald commented on HADOOP-3536:
    -----------------------------------------

    Pete,

    There's a few issues here:

    What does fuse support:
    * FUSE allows access to the user performing each operation.
    *FUSE allows attributes and permissions to be retrieved and set.

    What does fuse-dfs not support, but should:
    * fuse-dfs should access the DFS as the requesting user "asuser" (thereby upholding the hadoop security model)
    * fuse-dfs should allow permissions to be set & retrieved from the DFS

    fuse-dfs is bound by the API provided by libhdfs. In this case, the missing features are:
    * libhdfs should allow connection to the DFS as a given user
    * libhdfs should allow permissions to be set and retrieved. HADOOP-3264

    I will split this JIRA up into several issues:
    * fuse-dfs user impersonation
    * fuse-dfs permissions set & get
    And add the missing libhdfs dependent JIRA
    * Allow connecting username to be specified in libhdfs

    This JIRA will remain as an overview issue.
    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.
  • Craig Macdonald (JIRA) at Jul 13, 2008 at 3:57 pm
    [ https://issues.apache.org/jira/browse/HADOOP-3536?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12613170#action_12613170 ]

    craigm edited comment on HADOOP-3536 at 7/13/08 8:55 AM:
    ------------------------------------------------------------------

    Pete,

    There's a few issues here:

    What does fuse support:
    * FUSE allows access to the user performing each operation.
    * FUSE allows attributes and permissions to be retrieved and set.

    What does fuse-dfs not support, but should:
    * fuse-dfs should access the DFS as the requesting user "asuser" (thereby upholding the hadoop security model)
    * fuse-dfs should allow permissions to be set & retrieved from the DFS

    fuse-dfs is bound by the API provided by libhdfs. In this case, the missing features are:
    * libhdfs should allow connection to the DFS as a given user
    * libhdfs should allow permissions to be set and retrieved. HADOOP-3264

    I propose splitting this JIRA up into several issues:
    * fuse-dfs user impersonation
    * fuse-dfs permissions set & get

    And add the missing libhdfs dependent JIRA
    * Allow connecting username to be specified in libhdfs

    This JIRA will remain as an overview issue.

    was (Author: craigm):
    Pete,

    There's a few issues here:

    What does fuse support:
    * FUSE allows access to the user performing each operation.
    *FUSE allows attributes and permissions to be retrieved and set.

    What does fuse-dfs not support, but should:
    * fuse-dfs should access the DFS as the requesting user "asuser" (thereby upholding the hadoop security model)
    * fuse-dfs should allow permissions to be set & retrieved from the DFS

    fuse-dfs is bound by the API provided by libhdfs. In this case, the missing features are:
    * libhdfs should allow connection to the DFS as a given user
    * libhdfs should allow permissions to be set and retrieved. HADOOP-3264

    I will split this JIRA up into several issues:
    * fuse-dfs user impersonation
    * fuse-dfs permissions set & get
    And add the missing libhdfs dependent JIRA
    * Allow connecting username to be specified in libhdfs

    This JIRA will remain as an overview issue.
    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.
  • Pete Wyckoff (JIRA) at Jul 15, 2008 at 7:02 pm
    [ https://issues.apache.org/jira/browse/HADOOP-3536?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12613697#action_12613697 ]

    Pete Wyckoff commented on HADOOP-3536:
    --------------------------------------

    +1

    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.
  • Craig Macdonald (JIRA) at Jul 15, 2008 at 10:43 pm
    [ https://issues.apache.org/jira/browse/HADOOP-3536?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12613760#action_12613760 ]

    Craig Macdonald commented on HADOOP-3536:
    -----------------------------------------

    Done - I've split this issue into four sub-issues. Two are requirements for fuse-dfs, and there are two corresponding issues in libhdfs.


    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.
  • Pete Wyckoff (JIRA) at Sep 8, 2008 at 3:55 am
    [ https://issues.apache.org/jira/browse/HADOOP-3536?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

    Pete Wyckoff resolved HADOOP-3536.
    ----------------------------------

    Resolution: Duplicate
    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.

Related Discussions

Discussion Navigation
viewthread | post
Discussion Overview
groupcommon-dev @
categorieshadoop
postedJun 11, '08 at 5:55p
activeSep 8, '08 at 3:55a
posts16
users1
websitehadoop.apache.org...
irc#hadoop

1 user in discussion

Pete Wyckoff (JIRA): 16 posts

People

Translate

site design / logo © 2022 Grokbase