[
https://issues.apache.org/jira/browse/HDFS-4703?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Suresh Srinivas updated HDFS-4703:
----------------------------------
Resolution: Invalid
Status: Resolved (was: Patch Available)
Realized that the current AccessControlException only exposes the path up to
the point where the executable(/read) permission is set for the directory. So
this jira is not required.
> Permission checker should not expose resolved paths
> ---------------------------------------------------
>
> Key: HDFS-4703
> URL: https://issues.apache.org/jira/browse/HDFS-4703
> Project: Hadoop HDFS
> Issue Type: Improvement
> Components: namenode
> Reporter: Suresh Srinivas
> Attachments: HDFS-4703.patch
>
>
> Namenode currently prints inode information in AccessControlException. When
> path provided by user is different from the actual path is resolved to a
> different path in namenode (some examples as in snapshot paths, HDFS-4434),
> this might expose information about resolved path.
> In this jira, in permission checker, I propose adding a separate field for
> path to print in AccessControlException.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
