supervision - discussion about system services, daemon supervision, init, runlevel management, and tools such as s6 and runit
 help / color / mirror / Atom feed
From: "Laurent Bercot" <ska-supervision@skarnet.org>
To: "supervision@list.skarnet.org" <supervision@list.skarnet.org>
Subject: Re: Unprivileged Shutdown?
Date: Sat, 28 May 2022 08:43:51 +0000	[thread overview]
Message-ID: <emc5d7e355-36a6-4160-aff0-a3d908b90d5a@11e3bfd6.com> (raw)
In-Reply-To: <2NMWH7KWN9U8A.2QSU8NGDI39Q7@oak.localdomain>


>I have been using simple privilege escalation to poweroff the machine,
>but looking through the source code for s6-linux-init-shutdownd and
>friends, it appears the only constraint on interacting with the daemon
>is the permissions on run-image/service/s6-linux-init-shutdownd/fifo.
>
>The default appears to be:
>600 root root
>I've changed it on my system to be:
>620 root power
>and added my user to the power group.
>
>This seems like the cleanest way to implement unprivileged
>poweroff/reboot, but I'm concerned that it's not possible by default.
>Is there a better way, or is it just meant to be done manually?

  No, you are correct that it is the right mechanism.

  Allowing unprivileged shutdown is a dangerous operation and should
only be done is very specific circumstances (i.e. when a normal user
has complete seat and console access), so it's not the default and the
mechanism is fairly hidden.
  If there's demand, I can probably write a s6-linux-init-shutdown-perms
program in a future version that would let you specify the user/group
allowed to shutdown, rather than having you manually tinker with the
fifo.

--
  Laurent


      reply	other threads:[~2022-05-28  8:43 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-28  3:44 Dallin Dahl
2022-05-28  8:43 ` Laurent Bercot [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=emc5d7e355-36a6-4160-aff0-a3d908b90d5a@11e3bfd6.com \
    --to=ska-supervision@skarnet.org \
    --cc=supervision@list.skarnet.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).