From: Michael Tremer <michael.tremer@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: [PATCH] sysctl.conf: Turn on BPF JIT hardening, if the JIT is enabled
Date: Mon, 08 Jun 2020 10:07:52 +0100 [thread overview]
Message-ID: <E6F897A5-B099-4AEA-A53D-2563AEC0650F@ipfire.org> (raw)
In-Reply-To: <80294752-603e-be9a-9faf-5348116d3e09@ipfire.org>
[-- Attachment #1: Type: text/plain, Size: 1350 bytes --]
Hi Peter,
> On 7 Jun 2020, at 18:02, Peter Müller <peter.mueller(a)ipfire.org> wrote:
>
> This is recommended by the Kernel Self Protection Project, and although
> we do not take advantage of the BPF JIT at this time, we should set this
> nevertheless in order to avoid potential security vulnerabilities.
I do not really understand what you are trying to achieve here.
Please state more clearly *why* you think this is a useful change for IPFire.
As far as I am aware, the kernel internally uses BPF.
-Michael
P.S. How the f*** is this not already the default in the Linux kernel? Performance only, eh?
>
> Fixes: #12384
>
> Signed-off-by: Peter Müller <peter.mueller(a)ipfire.org>
> ---
> config/etc/sysctl.conf | 3 +++
> 1 file changed, 3 insertions(+)
>
> diff --git a/config/etc/sysctl.conf b/config/etc/sysctl.conf
> index 7e7ebee44..3f4c828f9 100644
> --- a/config/etc/sysctl.conf
> +++ b/config/etc/sysctl.conf
> @@ -49,6 +49,9 @@ kernel.dmesg_restrict = 1
> fs.protected_symlinks = 1
> fs.protected_hardlinks = 1
>
> +# Turn on BPF JIT hardening, if the JIT is enabled.
> +net.core.bpf_jit_harden = 2
> +
> # Minimal preemption granularity for CPU-bound tasks:
> # (default: 1 msec# (1 + ilog(ncpus)), units: nanoseconds)
> kernel.sched_min_granularity_ns = 10000000
> --
> 2.26.2
next prev parent reply other threads:[~2020-06-08 9:07 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-07 17:02 Peter Müller
2020-06-08 9:07 ` Michael Tremer [this message]
2020-06-09 18:00 ` Peter Müller
2021-04-02 19:37 ` Peter Müller
2021-04-06 10:10 ` Michael Tremer
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=E6F897A5-B099-4AEA-A53D-2563AEC0650F@ipfire.org \
--to=michael.tremer@ipfire.org \
--cc=development@lists.ipfire.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