[jira] [Updated] (SPARK-43368) Address DOI comments about /etc/passwd

["Sean R. Owen (Jira)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/SPARK-43368?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Sean R. Owen updated SPARK-43368:
---------------------------------
    Priority: Minor  (was: Major)

> Address DOI comments about /etc/passwd
> --------------------------------------
>
>                 Key: SPARK-43368
>                 URL: https://issues.apache.org/jira/browse/SPARK-43368
>             Project: Spark
>          Issue Type: Sub-task
>          Components: Spark Docker
>    Affects Versions: 3.5.0
>            Reporter: Yikun Jiang
>            Priority: Minor
>
> chgrp root /etc/passwd && chmod ug+rw /etc/passwd
> Wider permissions on /etc/passwd is concerning. What use case is broken if the running user id doesn't exist?
> echo ... >> /etc/passwd
> Having the entrypoint itself modify /etc/passwd is fragile. Are there features that are broken if the user doesn't exist in /etc/passwd (like PostgreSQL's initdb that refuses to run)? Minimally, this should probably use useradd and usermod rather than hand editing.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@spark.apache.org
For additional commands, e-mail: issues-help@spark.apache.org