From 1d1e3aefd7f1f8add2ee93863c046e92d72181ae Mon Sep 17 00:00:00 2001 From: Donald Buczek Date: Sat, 19 Dec 2020 13:30:13 +0100 Subject: [PATCH] Set perf_event_paranoid to -1 Set perf_event_paranoid to -1 as user requested. See [1] for implications. Security implication seems to be limited to information leak from kernel and "unfair" usage of memory available for perf data between users. So its no big deal. [1]: https://www.kernel.org/doc/html/latest/admin-guide/perf-security.html --- misc_etc_files/sysctl.conf | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/misc_etc_files/sysctl.conf b/misc_etc_files/sysctl.conf index 1887b7e..242ef18 100644 --- a/misc_etc_files/sysctl.conf +++ b/misc_etc_files/sysctl.conf @@ -44,4 +44,4 @@ kernel.shmall = 34359738368 # user request: Allow CPU event access by users without CAP_SYS_ADMIN -kernel.perf_event_paranoid = 1 +kernel.perf_event_paranoid = -1