[
https://issues.apache.org/jira/browse/MESOS-6526?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15654887#comment-15654887
]
Yan Xu commented on MESOS-6526:
-------------------------------
One follow-up commit.
{noformat:title=master}
commit 8a41c7692b629c3b4365cd6f8153a51b81e6c676
Author: Jiang Yan Xu <[email protected]>
Date: Tue Nov 8 13:11:07 2016 -0800
Fixed a macOS condition missed by ee08306.
{noformat}
{noformat:title=1.1.x}
commit d271d39f5cd1d2f186b37a1b86519b7a7de80ec5
Author: Jiang Yan Xu <[email protected]>
Date: Tue Nov 8 13:11:07 2016 -0800
Fixed a macOS condition missed by ee08306.
{noformat}
> `mesos-containerizer launch --environment` exposes executor env vars in `ps`.
> -----------------------------------------------------------------------------
>
> Key: MESOS-6526
> URL: https://issues.apache.org/jira/browse/MESOS-6526
> Project: Mesos
> Issue Type: Bug
> Components: containerization
> Affects Versions: 1.1.0
> Reporter: Yan Xu
> Assignee: Yan Xu
> Priority: Critical
> Fix For: 1.1.1, 1.2.0
>
>
> With MESOS-6323, the helper {{mesos-containerizer launch}} takes a
> `--environment` flag for the env vars used by the executor. This is
> unpleasant because its a common practice that people use env vars to hide
> configs that are sensitive and now it's visible to non-root users on the host
> with a {{ps}} command.
> Given that we want to separate the environments of {{mesos-containerizer
> launch}} and the executor itself, perhaps we can just package and serialize
> the executor env vars in one env var {{MESOS_EXECUTOR_ENVIRONMENT}} and pass
> that to {{mesos-containerizer launch}} which could then get it through a flag
> the usual way.
> In general Mesos should do more to protect env vars but I'll file separate
> issues for them.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
