You are viewing a plain text version of this content. The canonical link for it is here.

Posted to commits@airflow.apache.org by "jack (JIRA)" <ji...@apache.org> on 2018/12/12 17:41:00 UTC

[jira] [Commented] (AIRFLOW-1536) DaemonContext uses default umask 0

    [ https://issues.apache.org/jira/browse/AIRFLOW-1536?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16719251#comment-16719251 ] 

jack commented on AIRFLOW-1536:
-------------------------------

this could be a venerability though I'm not sure it's urgent to fix.

> DaemonContext uses default umask 0
> ----------------------------------
>
>                 Key: AIRFLOW-1536
>                 URL: https://issues.apache.org/jira/browse/AIRFLOW-1536
>             Project: Apache Airflow
>          Issue Type: Bug
>          Components: cli, security
>            Reporter: Timothy O'Keefe
>            Priority: Major
>
> All DaemonContext instances used for worker, scheduler, webserver, flower, etc. do not supply a umask argument. See here for example:
> https://github.com/apache/incubator-airflow/blob/b0669b532a7be9aa34a4390951deaa25897c62e6/airflow/bin/cli.py#L869
> As a result, the DaemonContext will use the default umask=0 which leaves user data exposed. A BashOperator for example that writes any files would have permissions rw-rw-rw- as would any airflow logs.
> I believe the umask should either be configurable, or inherited from the parent shell, or both.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)