diff options
author | Wojtek Kosior <koszko@koszko.org> | 2024-01-09 12:15:02 +0100 |
---|---|---|
committer | Wojtek Kosior <koszko@koszko.org> | 2024-01-22 21:18:53 +0100 |
commit | cde0ea6ba5de37154ba8ce48d5d33fcd39f154c8 (patch) | |
tree | 3503df7034d143944e28956f71d420ce93d2def2 /gnu/packages | |
parent | ed03ee42a204984254628a038f4c8c2beec2010a (diff) | |
download | guix-cde0ea6ba5de37154ba8ce48d5d33fcd39f154c8.tar.gz guix-cde0ea6ba5de37154ba8ce48d5d33fcd39f154c8.zip |
services: Support running Exim with setuid/setgid.
In a typical configuration, Exim binary is setuid root and the Exim daemon
process listens for connections under a non-root system account (usually
`exim`). Upon receiving a message, it forks into a child process which
re-executes the binary to regain privileges and deliver the mail to its
destination (e.g. a Maildir inside user's home directory).
Besides the setuid binary itself, such setup also requires the Exim
configuration file to live at the path Exim considers safe. It defaults to
/etc/exim.conf and changing it requires rebuilding the Exim daemon. If a
configuration at unsafe path is used instead, Exim drops its privileges before
reading it and becomes unable to perform certain kinds of email delivery.
* gnu/services/mail.scm (<exim-configuration>)[setuid-user]: New field.
(<exim-configuration>)[setgid-group]: New field.
(exim-computed-config-file): Delete variable.
(exim-shepherd-service)[start]: Use Exim's default config at /etc/exim.conf.
(exim-activation): Atomically put Exim's current config at /etc/exim.conf and
verify its syntactic correctness.
(exim-setuids): New variable.
(exim-service-type)[extensions]: Extend `setuid-program-service-type`.
Change-Id: Ie6153baac80180d3d48f6b5a6959895df06aef0b
Diffstat (limited to 'gnu/packages')
0 files changed, 0 insertions, 0 deletions