diff options
author | Michael Olbrich <m.olbrich@pengutronix.de> | 2020-08-07 12:34:15 +0200 |
---|---|---|
committer | Michael Olbrich <m.olbrich@pengutronix.de> | 2020-08-14 14:24:51 +0200 |
commit | 116c4c1c0a80193fc63646a30e12ccc28fc0f29f (patch) | |
tree | 671275f2d5fb4b3b7adea3d17a30b914c577b4bc /doc | |
parent | d1c7aafe9da79ad50d451837439ec98951581a03 (diff) | |
download | ptxdist-116c4c1c0a80193fc63646a30e12ccc28fc0f29f.tar.gz ptxdist-116c4c1c0a80193fc63646a30e12ccc28fc0f29f.tar.xz |
ptxdist: improve umask handling
Currently any umask other than 0022 is not really supported. There is no
check but strange things may happen, either at build-time or at runtime.
Improve this by:
- setting the umask to 0022 if it it currently more permissive
- fail with a clear error message if it is more restrictive
Expand the documentation to explain the new behaviour.
Signed-off-by: Michael Olbrich <m.olbrich@pengutronix.de>
Diffstat (limited to 'doc')
-rw-r--r-- | doc/daily_work.inc | 8 |
1 files changed, 8 insertions, 0 deletions
diff --git a/doc/daily_work.inc b/doc/daily_work.inc index a37aac4c3..ca3ea6903 100644 --- a/doc/daily_work.inc +++ b/doc/daily_work.inc @@ -1372,6 +1372,14 @@ a different ``umask`` than ``0022`` at build-time this may fail badly at run-time with strange erroneous behaviour (for example some daemons with regular user permissions cannot access their own configuration files). +If the current ``umask`` is more permissive than the required ``umask``, +then ptxdist will change it as required. For example, a ``umask`` of +``0002`` is quite common when the primary group of a user has the same name +as the user. + +For security reasons, PTXdist will not set a more permissive ``umask`` +than the current one. + Read Only Filesystem -------------------- |