infra-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Gavin (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (INFRA-14471) Hermes: ensure new apmail files/dirs have group:r(+x) perms
Date Thu, 13 Dec 2018 14:35:00 GMT

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

Gavin commented on INFRA-14471:
-------------------------------

This works fine now.

[apmail@hermes lists]$ ls -l iceberg.apache.org/issues/
total 70
-rwxr-xr--  1 apmail  apmail  273 Dec 13 12:30 Log
drwxr-xr--  3 apmail  apmail    5 Dec 13 12:30 allow



> Hermes: ensure new apmail files/dirs have group:r(+x) perms
> -----------------------------------------------------------
>
>                 Key: INFRA-14471
>                 URL: https://issues.apache.org/jira/browse/INFRA-14471
>             Project: Infrastructure
>          Issue Type: Task
>          Components: Mailing Lists
>            Reporter: Sebb
>            Assignee: Gavin
>            Priority: Major
>              Labels: pull-request-available
>
> It was agreed that the apmail group should have read access to files/dirs under apmail.
This means apmail users can avoid using sudo except when they need to update something. Also
group read access is necessary for an apmail read-only role (INFRA-14404).
> It appears that new mailing lists are being created without the required access. 
> Not sure how best to fix this. There are various options:
> - update the mail creation script so it creates files/dirs with the desired permissions
(umask ?)
> - update the script to chmod the new part of directory tree just before exit
> - add default ACLs to apmail directories
> - add a cronjob to fix the incorrect permissions
> - something else?



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

Mime
View raw message