From: Maxim Cournoyer <maxim.cournoyer@gmail.com>
To: Florian Dold <florian.dold@gmail.com>
Cc: 33966@debbugs.gnu.org
Subject: [bug#33966] fcgiwrap: additional options for logging and unix domain sockets
Date: Mon, 11 Nov 2024 21:41:11 +0900 [thread overview]
Message-ID: <87ed3i9c48.fsf@gmail.com> (raw)
In-Reply-To: <624ba072-d5fe-b159-46af-61e79caf22f1@gmail.com> (Florian Dold's message of "Thu, 3 Jan 2019 21:02:38 +0100")
Hi Florian,
Florian Dold <florian.dold@gmail.com> writes:
> Hi Guix,
>
> this patch adds additional options to the fcgiwrap service. In
> particular it allows
>
> 1. writing the output of the fcgi process to a file (with the 'log-file'
> option)
>
> 2. arranging for a directory to be created so that the fcgiwrap process
> can create its listening socket without running into permission problems
> (with the 'ensure-socket-dir?' option)
>
> 3. adjusting the permissions on the listening unix domain socket,
> typically so that users in the fcgiwrap group have read and write access
> to that socket (with the 'adjusted-socket-permissions' option)
>
> Additionally, a potentially left-over fcgiwrap socket is cleaned up
> before starting the service, which would otherwise lead to the process
> refusing to run.
>
> The documentation is also changed to address a potential security issue,
> now recommending against running fcgiwrap as root.
>
> The configuration defaults are not ideal (a tcp socket with unrestricted
> access from any local user), but impossible to change without breaking
> existing system definitions.
Unfortunately this great patch no longer applies cleanly (there are
conflicts in the doc). Would you be so kind as to resend an updated
version?
--
Thanks,
Maxim
prev parent reply other threads:[~2024-11-11 12:43 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-03 20:02 [bug#33966] fcgiwrap: additional options for logging and unix domain sockets Florian Dold
2019-01-09 16:17 ` Ludovic Courtès
2019-05-25 7:57 ` Arun Isaac
2024-11-11 12:41 ` Maxim Cournoyer [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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87ed3i9c48.fsf@gmail.com \
--to=maxim.cournoyer@gmail.com \
--cc=33966@debbugs.gnu.org \
--cc=florian.dold@gmail.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.savannah.gnu.org/cgit/guix.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).