Problem/Motivation

In #2232051-24: Unnessessary chmod during config write we minimize amount of chmod() operations for config writes and was pointed in comments #2 and #3 it's for "historical reasons" as changing owner is unpredictable when Linux using ACLs

Steps to reproduce

In #2232051-3: Unnessessary chmod during config write and previous comment

Proposed resolution

- Using umask() and possible some PHP wrapper for ALCs will allow broader access permissions managment
- discover how to use umask() one per serving request as #2232051-24: Unnessessary chmod during config write suggests and get rid of chmod() after each write as all writes should be controlled throw filesystem streams or kinda that level (stream context maybe)

Remaining tasks

- research, centralize writes
- setting umask() per request

User interface changes

No

API changes

TBD

Data model changes

No

Release notes snippet

No

Comments

andypost created an issue. See original summary.

andypost’s picture

andypost
he/him
Primary language Russian
commented

As a follow-up task it also makes second question about ACL support for files

it depends on php-fpm build flag to use --with-fpm-acl

So PHP 8.0+ has full support of acl

Version: 10.1.x-dev » 11.x-dev

Drupal core is moving towards using a “main” branch. As an interim step, a new 11.x branch has been opened, as Drupal.org infrastructure cannot currently fully support a branch named main. New developments and disruptive changes should now be targeted for the 11.x branch, which currently accepts only minor-version allowed changes. For more information, see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.

Version: 11.x-dev » main

Drupal core is now using the main branch as the primary development branch. New developments and disruptive changes should now be targeted to the main branch.

Read more in the announcement.