From: Remco van 't Veer <remco@remworks.net>
To: Tobias Geerinckx-Rice <me@tobias.gr>
Cc: Ekaitz Zarraga <ekaitz@elenq.tech>,
Christian Gelinek <christian.gelinek@mailbox.org>,
help-guix@gnu.org
Subject: Re: Disabling unprivileged BPF by default in our kernels
Date: Thu, 02 Feb 2023 18:13:45 +0100 [thread overview]
Message-ID: <87lelg56t2.fsf@remworks.net> (raw)
In-Reply-To: <87bkmdnp69.fsf@nckx>
2023/02/01 20:43, Tobias Geerinckx-Rice:
>> What does Debian's kconfig list for CONFIG_BPF_UNPRIV_DEFAULT_OFF?
>
> I've always had this option set to Y in my own kernels, and it has
> never so much as inconvenienced me. However, I'm not a BPF power
> user.
>
> Does anyone know any serious and concrete drawbacks to setting this
> option in all Guix kernels, to increase default security & better
> align with other major distros?
There is a linux-libre-bpf package so I'd expect BPF power users to use
that. So I guess adding it to the default-extra-linux-options should be
fine.
R.
next prev parent reply other threads:[~2023-02-02 17:16 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-01 10:21 Intel i7-1165G7 vulnerable to Spectre v2 Christian Gelinek
2023-02-01 14:20 ` Felix Lechner via
2023-02-03 9:59 ` Christian Gelinek
2023-02-01 15:58 ` Tobias Geerinckx-Rice
2023-02-01 18:29 ` Ekaitz Zarraga
2023-02-01 19:43 ` Disabling unprivileged BPF by default in our kernels Tobias Geerinckx-Rice
2023-02-02 11:40 ` Leo Famulari
2023-02-02 17:13 ` Remco van 't Veer [this message]
2023-02-02 17:19 ` Tobias Geerinckx-Rice
2023-02-03 10:13 ` Intel i7-1165G7 vulnerable to Spectre v2 Christian Gelinek
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=87lelg56t2.fsf@remworks.net \
--to=remco@remworks.net \
--cc=christian.gelinek@mailbox.org \
--cc=ekaitz@elenq.tech \
--cc=help-guix@gnu.org \
--cc=me@tobias.gr \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).