[
https://issues.apache.org/jira/browse/HDDS-1712?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16886343#comment-16886343
]
Eric Yang commented on HDDS-1712:
---------------------------------
{quote}See my comment in the pull request, this is an independent problem. Even
without sudo I can do the same (use ubuntu image + mount host path){quote}
Please demonstrate. If -u ${UID}:${GID} is enforced, and UID does not have
sudo access, and host mounting paths are permissively allowed? docker -u flag
and mounting path can be audited before source code is committed. By
implementing a few simple procedures, this will make Ozone docker image more
secure and less abuse on root power. We should not provide false impression to
user that we are starting with -u hadoop, then go behind user's back to run
sudo curl install. Otherwise, it breaks user's trust to use Ozone-runner image.
> Remove sudo access from Ozone docker image
> ------------------------------------------
>
> Key: HDDS-1712
> URL: https://issues.apache.org/jira/browse/HDDS-1712
> Project: Hadoop Distributed Data Store
> Issue Type: Bug
> Reporter: Eric Yang
> Assignee: Eric Yang
> Priority: Major
> Labels: pull-request-available
> Attachments: HDDS-1712.001.patch
>
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> Ozone docker image is given unlimited sudo access to hadoop user. This poses
> a security risk where host level user uid 1000 can attach a debugger to the
> container process to obtain root access.
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)
---------------------------------------------------------------------
To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
