[ https://issues.apache.org/jira/browse/HDFS-5923?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13897475#comment-13897475 ]
Fengdong Yu commented on HDFS-5923: ----------------------------------- Thanks Zhao Jing. Another question, HDFS-5968 has serialized FsImage using Protobuf, then does that also serialized ACL states? I don't think we've done it. because HDFS-4685 not merged to trunk yet. > Do not persist the ACL bit in the FsPermission > ---------------------------------------------- > > Key: HDFS-5923 > URL: https://issues.apache.org/jira/browse/HDFS-5923 > Project: Hadoop HDFS > Issue Type: Sub-task > Components: hdfs-client, namenode, security > Reporter: Haohui Mai > Assignee: Haohui Mai > > The current implementation persists and ACL bit in FSImage and editlogs. > Moreover, the security decisions also depend on whether the bit is set. > The problem here is that we have to maintain the implicit invariant, which is > the ACL bit is set if and only if the the inode has AclFeature. The invariant > has to be maintained everywhere otherwise it can lead to a security > vulnerability. In the worst case, an attacker can toggle the bit and bypass > the ACL checks. > The jira proposes to treat the ACL bit as a transient bit. The bit should not > be persisted onto the disk, neither it should affect any security decisions. -- This message was sent by Atlassian JIRA (v6.1.5#6160)