Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.kernel > #1425437
| From | Arnaldo Carvalho de Melo <acme@kernel.org> |
|---|---|
| Newsgroups | linux.kernel |
| Subject | Re: [kernel-hardening] [PATCH 2/2] security,perf: Allow further restriction of perf_event_open |
| Date | 2016-06-17 22:10 +0200 |
| Message-ID | <rL8fw-2Ds-49@gated-at.bofh.it> (permalink) |
| References | <qPMzU-4ae-19@gated-at.bofh.it> <rL4EV-my-1@gated-at.bofh.it> |
| Organization | linux.* mail to news gateway |
Em Fri, Jun 17, 2016 at 12:16:47PM -0400, Daniel Micay escreveu: > On Fri, 2016-06-17 at 08:54 +0200, Peter Zijlstra wrote: > > This Changelog is completely devoid of information. _WHY_ are you > > doing this? > Attack surface reduction. It's possible to use seccomp-bpf for some > limited cases, but it's not flexible enough. There are lots of > information leaks and local privilege escalation vulnerabilities via > perf events, yet on most Linux installs it's not ever being used. So > turning it off by default on those installs is an easy win. The holes > are reduced to root -> kernel (and that's not a meaningful boundary in > mainline right now - although as is the case here, Debian has a bunch of > securelevel patches for that). Is ptrace also disabled on such systems, or any of the other more recent syscalls? The same arguments could probably be used to disable those: reduce attack surface, possibly the new ones have bugs as they are relatively new and it takes a long time for new syscalls to be more generally used, if we go on disabling them in such a way, they will probably never get used :-\ Wouldn't the recent bump in perf_event_paranoid to 2 enough? I.e. only allow profiling of user tasks? Or is there something more specific that we should disable/constrain to reduce such surface contact without using such a big hammer? - Arnaldo
Back to linux.kernel | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
Re: [kernel-hardening] [PATCH 2/2] security,perf: Allow further restriction of perf_event_open Kees Cook <keescook@chromium.org> - 2016-06-17 00:30 +0200
Re: [kernel-hardening] [PATCH 2/2] security,perf: Allow further restriction of perf_event_open Peter Zijlstra <peterz@infradead.org> - 2016-06-17 09:00 +0200
Re: [kernel-hardening] [PATCH 2/2] security,perf: Allow further restriction of perf_event_open Daniel Micay <danielmicay@gmail.com> - 2016-06-17 18:20 +0200
Re: [kernel-hardening] [PATCH 2/2] security,perf: Allow further restriction of perf_event_open Arnaldo Carvalho de Melo <acme@kernel.org> - 2016-06-17 22:10 +0200
Re: [kernel-hardening] [PATCH 2/2] security,perf: Allow further restriction of perf_event_open Daniel Micay <danielmicay@gmail.com> - 2016-06-18 03:00 +0200
csiph-web