hadoop-common-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hairong Kuang (JIRA)" <j...@apache.org>
Subject [jira] Commented: (HADOOP-2543) No-permission-checking mode for smooth transition to 0.16's permissions features.
Date Mon, 14 Jan 2008 19:52:34 GMT

    [ https://issues.apache.org/jira/browse/HADOOP-2543?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12558756#action_12558756

Hairong Kuang commented on HADOOP-2543:

a) and c) have already been implemented in HADOOP-1298. I will work on b). In addition, I'd
like to make some change to the upgrade.
1) all files and directories will be owned by the super user and super group;
2) the permission of the files is set to be 0600 and the permission of the directories is
set to be 0700.
These changes make sure that files/directories won't be accessed by illegal users even when
an administrator forget to change their permissions when permission checking is turned on.

> No-permission-checking mode for smooth transition to 0.16's permissions features. 
> ----------------------------------------------------------------------------------
>                 Key: HADOOP-2543
>                 URL: https://issues.apache.org/jira/browse/HADOOP-2543
>             Project: Hadoop
>          Issue Type: New Feature
>          Components: dfs
>    Affects Versions: 0.15.1
>            Reporter: Sanjay Radia
>            Assignee: Hairong Kuang
>             Fix For: 0.16.0
> In moving to 0.16,  which will support permissions, a mode of no-permission checking
has been proposed to allow smooth transition to using the new permissions feature.
> The idea is that at first 0.16 will be used for a period of time with permission checking
> Later after the admin has changed ownership and permissions of various files, the permission
checking can be turned off.
> This Jira defines what the semantics are of the no-permission-checking mode.

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message