infra-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF subversion and git services (JIRA)" <>
Subject [jira] [Commented] (INFRA-14471) Hermes: ensure new apmail files/dirs have group:r(+x) perms
Date Mon, 10 Dec 2018 14:53:00 GMT


ASF subversion and git services commented on INFRA-14471:

Commit 763e990b0ee6b467a126f282a7b2fadf5c61044e in infrastructure-puppet's branch refs/heads/deployment
from [~cthistle]
[;h=763e990 ]

Merge pull request #1261 from apache/gm/INFRA-14471

Fixup perms of newly created list INFRA-14471

> Hermes: ensure new apmail files/dirs have group:r(+x) perms
> -----------------------------------------------------------
>                 Key: INFRA-14471
>                 URL:
>             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

View raw message