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

Posted to issues@mesos.apache.org by "James Peach (JIRA)" <ji...@apache.org> on 2017/05/24 23:54:04 UTC

[jira] [Issue Comment Deleted] (MESOS-7476) Restrict capabilities to only the bounding set.

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

James Peach updated MESOS-7476:
-------------------------------
    Comment: was deleted

(was: | [https://reviews.apache.org/r/59183/|https://reviews.apache.org/r/59183/] | Refactor setting capabilities into a helper function. |
| [https://reviews.apache.org/r/59184/|https://reviews.apache.org/r/59184/] | Add support for explicitly setting bounding capabilities. |)

> Restrict capabilities to only the bounding set.
> -----------------------------------------------
>
>                 Key: MESOS-7476
>                 URL: https://issues.apache.org/jira/browse/MESOS-7476
>             Project: Mesos
>          Issue Type: Bug
>          Components: containerization
>            Reporter: James Peach
>            Assignee: James Peach
>
> As a security improvement, it would be useful to be able to set the bounding capability set without also granting those capabilities. This is what the {{--allowed_capabilities}} flag sounds like it does.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)