You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@mesos.apache.org by "Gavin (JIRA)" <ji...@apache.org> on 2019/04/29 09:27:42 UTC

[jira] [Issue Comment Deleted] (MESOS-5615) When using command executor, the ExecutorInfo is useless for sandbox authorization

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

Gavin updated MESOS-5615:
-------------------------
    Comment: was deleted

(was: www.rtat.net)

> When using command executor, the ExecutorInfo is useless for sandbox authorization
> ----------------------------------------------------------------------------------
>
>                 Key: MESOS-5615
>                 URL: https://issues.apache.org/jira/browse/MESOS-5615
>             Project: Mesos
>          Issue Type: Bug
>          Components: agent, modules, security
>    Affects Versions: 1.0.0
>            Reporter: Alexander Rojas
>            Assignee: Jörg Schad
>            Priority: Blocker
>              Labels: authorization, mesosphere, modularization, security
>             Fix For: 1.0.0
>
>
> The design for sandbox access authorization uses the {{ExecutorInfo}} associated with the task as the main authorization space and the {{FrameworkInfo}} as a secondary one. This allows module writes to use fields such a labels for authorization.
> When a task uses the _command executor_ it doesn't provide an {{ExecutorInfo}}, but the info object is generated automatically inside the agent. As such, information which could be used for authorization (e.g. labels) is not available for authorization.



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