From: Matias Fonzo <selk@dragora.org>
To: musl@lists.openwall.com
Subject: Re: [PATCH] remaining steps for time64 switchover
Date: Mon, 28 Oct 2019 18:31:27 -0300 [thread overview]
Message-ID: <b91679e0a3f16e1ab86e8a6981a2d20a@dragora.org> (raw)
In-Reply-To: <ema77cb455-bd2e-4f85-861e-3e2ee557e99a@elzian>
Hi Laurent,
Thanks for the explanation and to give more details about it. :-)
El 2019-10-27 20:27, Laurent Bercot escribió:
>
> There is a run-time requirement for s6, but it's not an absolute one:
> the utmps-utmpd and utmps-wtmpd programs simply rely on an interface
> provided by s6-ipcserver(d). If you can provide the same interface,
> you can do without s6.
>
> utmps-utmpd and utmps-wtmpd expect:
> - to be launched via an inetd-like listening on the configured Unix
> domain socket, with stdin reading from the client and stdout writing
> to the client.
> - some environment variables:
> * PROTO must be set to IPC.
> * IPCREMOTEEUID must be set to the effective uid of the client.
> * IPCREMOTEEGID must be set to the effective gid of the client.
> Those last two are obtained on Linux via a struct ucred and the
> SO_PEERCRED option to getsockopt(). You can't fake that, it's the
> very reason why utmps is secure.
>
> Of course, you could also package s6 in Dragora. If you already have
> a perp supervision tree, you don't even have to run a s6 one. On the
> other hand, that's a risky proposition, because you might end up liking
> it and wanting to use it more. %-)
>
> --
> Laurent
next prev parent reply other threads:[~2019-10-28 21:31 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-21 2:46 Rich Felker
2019-10-21 12:43 ` Rich Felker
2019-10-27 4:15 ` Rich Felker
2019-10-27 4:26 ` Rich Felker
2019-10-27 8:32 ` Laurent Bercot
2019-10-27 14:53 ` Rich Felker
2019-10-27 20:12 ` Matias Fonzo
2019-10-27 21:14 ` Rich Felker
2019-10-27 21:53 ` Matias Fonzo
2019-10-27 23:27 ` Laurent Bercot
2019-10-28 21:31 ` Matias Fonzo [this message]
2019-10-28 22:22 ` Rich Felker
2019-10-29 19:52 ` Rich Felker
2019-10-29 19:53 ` Rich Felker
2019-10-29 23:08 ` Rich Felker
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=b91679e0a3f16e1ab86e8a6981a2d20a@dragora.org \
--to=selk@dragora.org \
--cc=musl@lists.openwall.com \
/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.
Code repositories for project(s) associated with this public inbox
https://git.vuxu.org/mirror/musl/
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).