From: q66 <q66@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Merged]: dhcpcd: make privsep a build option and disable it
Date: Tue, 17 Nov 2020 12:34:48 +0100 [thread overview]
Message-ID: <20201117113448.43DR5YCvQASq0_u9BjINA8_VjaD-BiLThyYqsLv9fIU@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-26451@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 509 bytes --]
There's a merged pull request on the void-packages repository
dhcpcd: make privsep a build option and disable it
https://github.com/void-linux/void-packages/pull/26451
Description:
dhcpcd's privsep is seccomp based and thus shits the bed on a whim (e.g.
different CPU architectures or upstream libc changes).
Disable it by default, but leave the option around if somebody really
needs it (hint: they can probably just use the AppArmor profile).
@Skirmisher care to test if this fixes the fork bomb?
@sgn
next prev parent reply other threads:[~2020-11-17 11:34 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-17 3:36 [PR PATCH] " CameronNemo
2020-11-17 3:59 ` [PR REVIEW] " ericonr
2020-11-17 4:18 ` Skirmisher
2020-11-17 4:20 ` Skirmisher
2020-11-17 11:11 ` [PR REVIEW] " q66
2020-11-17 11:34 ` q66 [this message]
2020-11-17 12:49 ` Duncaen
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=20201117113448.43DR5YCvQASq0_u9BjINA8_VjaD-BiLThyYqsLv9fIU@z \
--to=q66@users.noreply.github.com \
--cc=ml@inbox.vuxu.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).