hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Xiaoyu Yao (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HDFS-10324) Trash directory in an encryption zone should be pre-created with sticky bit
Date Mon, 25 Apr 2016 17:24:13 GMT

    [ https://issues.apache.org/jira/browse/HDFS-10324?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15256633#comment-15256633
] 

Xiaoyu Yao commented on HDFS-10324:
-----------------------------------

[~jojochuang], I mentioned #2 because Trash is client feature that used to not require file
system operation like {{hdfs dfs -mkdir /ez/tmp; hdfs dfs -chmod 1777 /ez/tmp}} for its operation.
Since this is encryption zone specific, it might be easier to have a single crytoadmin cmd
to handle it.

> Trash directory in an encryption zone should be pre-created with sticky bit
> ---------------------------------------------------------------------------
>
>                 Key: HDFS-10324
>                 URL: https://issues.apache.org/jira/browse/HDFS-10324
>             Project: Hadoop HDFS
>          Issue Type: Bug
>          Components: encryption
>    Affects Versions: 2.8.0
>         Environment: CDH5.7.0
>            Reporter: Wei-Chiu Chuang
>            Assignee: Wei-Chiu Chuang
>         Attachments: HDFS-10324.001.patch, HDFS-10324.002.patch
>
>
> We encountered a bug in HDFS-8831:
> After HDFS-8831, a deleted file in an encryption zone is moved to a .Trash subdirectory
within the encryption zone.
> However, if this .Trash subdirectory is not created beforehand, it will be created and
owned by the first user who deleted a file, with permission drwx------. This creates a serious
bug because any other non-privileged user will not be able to delete any files within the
encryption zone, because they do not have the permission to move directories to the trash
directory.
> We should fix this bug, by pre-creating the .Trash directory with sticky bit.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message