all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Leo Famulari <leo@famulari.name>
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, 2 Feb 2023 12:40:37 +0100	[thread overview]
Message-ID: <Y9uhNTBA3GRFMFzo@jasmine.lan> (raw)
In-Reply-To: <87bkmdnp69.fsf@nckx>

[-- Attachment #1: Type: text/plain, Size: 533 bytes --]

On Wed, Feb 01, 2023 at 08:43:42PM +0100, Tobias Geerinckx-Rice wrote:
> Ekaitz Zarraga 写道:
> > 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?

I have no opinion either way.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  reply	other threads:[~2023-02-02 11:41 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 [this message]
2023-02-02 17:13       ` Remco van 't Veer
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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=Y9uhNTBA3GRFMFzo@jasmine.lan \
    --to=leo@famulari.name \
    --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.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/guix.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.