You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@mesos.apache.org by "Alex Clemmer (JIRA)" <ji...@apache.org> on 2015/11/06 07:10:27 UTC

[jira] [Updated] (MESOS-3412) Revisit Unix-to-Windows permissions mapping

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

Alex Clemmer updated MESOS-3412:
--------------------------------
    Target Version/s:   (was: 0.26.0)

> Revisit Unix-to-Windows permissions mapping
> -------------------------------------------
>
>                 Key: MESOS-3412
>                 URL: https://issues.apache.org/jira/browse/MESOS-3412
>             Project: Mesos
>          Issue Type: Task
>          Components: stout
>            Reporter: Alex Clemmer
>            Assignee: Alex Clemmer
>              Labels: mesosphere, permissions, stout, windows
>
> In review https://reviews.apache.org/r/37032/ there was some debate about how to handle "fallback" of setting/getting Unix permissions on Windows. That is, on Windows there is not native support for "group" or "other" permissions, so when a user gets/sets group permissions, we can either (1) make that operation a no-op, or (2) "fall back" to getting/setting "user" permissions.
> Originally the review opted for a "strictness" flag, so that at compile time users could pass in a flag and change the "fallback" behavior to be "strict" instead, ignoring group and other permissions setting.
> Currently (Sept 10 2015) we have pulled this option out, and only allow "strict" permissions. This will probably break stuff later, but we can reevaluate later.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)