From 8c22e88befbd6ce76acdc9371683dca43425235e Mon Sep 17 00:00:00 2001 From: Laurent Bercot Date: Mon, 4 Feb 2019 20:20:54 +0000 Subject: Scrap s6-rc-compile -u/-g, implement uid/self instead. Prepare for 0.5.0.0 --- doc/s6-rc-compile.html | 32 +++++--------------------------- 1 file changed, 5 insertions(+), 27 deletions(-) (limited to 'doc/s6-rc-compile.html') diff --git a/doc/s6-rc-compile.html b/doc/s6-rc-compile.html index 57a6b95..d931b91 100644 --- a/doc/s6-rc-compile.html +++ b/doc/s6-rc-compile.html @@ -36,7 +36,7 @@ the current service database via

Interface

-     s6-rc-compile [ -v verbosity ] [ -u uids ] [ -g gids ] [ -h fdhuser ]  [ -b ] compiled source...
+     s6-rc-compile [ -v verbosity ] [ -h fdhuser ]  [ -b ] compiled source...
 
-

- If the -u or -g option is used, then 0 -must be explicitly listed in uids in order to allow root -to operate the database. If neither option is used, then root -(and only root) is implicitly allowed. -

- -

- It is important to only use the -u or -g -options when the user owning the supervision tree is not root. The -internal s6-rc mechanisms allow uids and gids specified by those -options to run any oneshot in the compiled service database as the -user owning the supervision tree; -if that user is root, this becomes an avenue for unwanted -privilege gain. Only specify users that have the right to operate -the supervision tree! -

-

Source format

@@ -408,6 +382,10 @@ following an invocation of s6-rc-init or and it must not be deleted. The only way to "free" such a compiled database for displacement or deletion is to replace it as the live one via another call to s6-rc-update. +

  • No matter what user compiles the database, only root and the +user owning the supervision tree at run-time will be able +to operate the compiled database with the s6-rc +command.
  • -- cgit v1.2.3