[
https://issues.apache.org/jira/browse/HADOOP-4104?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12629042#action_12629042
]
Craig Macdonald commented on HADOOP-4104:
-----------------------------------------
My understanding is that Hadoop has no real authentication in it - it just
assumes that what UGI gives is correct. This is possibly the first scenario
where we're bending UGI to give something different. That being the case, we
should provide the security.
I think any security checks in Hadoop will depend how Hadoop implements
authentication and security in due course. In the meantime, it's probably good
that we enforce some security in the mean time.
My understanding from
http://en.allexperts.com/q/Unix-Linux-OS-1064/real-effective-user-id.htm is
that what we want to check is effective uid. whoami (at least on linux) will
return euid, not uid.
> add time, permission and user attribute support to libhdfs
> ----------------------------------------------------------
>
> Key: HADOOP-4104
> URL: https://issues.apache.org/jira/browse/HADOOP-4104
> Project: Hadoop Core
> Issue Type: New Feature
> Components: libhdfs
> Reporter: Pete Wyckoff
> Assignee: Pete Wyckoff
> Fix For: 0.19.0
>
> Attachments: HADOOP-4104.txt
>
>
> 1. add mtime, accesstime, owner, permissions to HDFSFileInfo
> 2. create hdfsChown, hdfsChmod, hdfsUtime functions
> 3. create hdfsConnectAsUser function
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
