From: Yu Watanabe Date: Mon, 7 Aug 2017 09:02:47 +0000 (+0900) Subject: man: DynamicUser= does not imply PrivateDevices= (#6510) X-Git-Tag: v235~262 X-Git-Url: http://git.ipfire.org/gitweb.cgi?a=commitdiff_plain;h=2d35b79cdc65952a71b768f4fc0e2134a47e0294;p=thirdparty%2Fsystemd.git man: DynamicUser= does not imply PrivateDevices= (#6510) Follow-up for effbd6d2eadb61bd236d118afc7901940c4c6b37. --- diff --git a/man/systemd.exec.xml b/man/systemd.exec.xml index b074331dd59..b3495c97857 100644 --- a/man/systemd.exec.xml +++ b/man/systemd.exec.xml @@ -1079,12 +1079,10 @@ services which shall be able to install mount points in the main mount namespace. The new /dev will be mounted read-only and 'noexec'. The latter may break old programs which try to set up executable memory by using mmap2 of - /dev/zero instead of using MAP_ANON. This setting is implied if - DynamicUser= is set. For this setting the same restrictions regarding mount propagation and - privileges apply as for ReadOnlyPaths= and related calls, see above. + /dev/zero instead of using MAP_ANON. For this setting the same restrictions + regarding mount propagation and privileges apply as for ReadOnlyPaths= and related calls, see above. If turned on and if running in user mode, or in system mode, but without the CAP_SYS_ADMIN - capability (e.g. setting User=), NoNewPrivileges=yes - is implied. + capability (e.g. setting User=), NoNewPrivileges=yes is implied. Note that the implementation of this setting might be impossible (for example if mount namespaces