From: "Peter Müller" <peter.mueller@link38.eu>
To: development@lists.ipfire.org
Subject: [PATCH v2] hide kernel addresses in /proc against privileged users
Date: Mon, 21 Jan 2019 21:43:26 +0100 [thread overview]
Message-ID: <cb91cffd-10e2-c075-ec92-90fa8290eb71@link38.eu> (raw)
In-Reply-To: <B2B43E94-7188-46F9-AD19-5D2F1E1D9EC6@ipfire.org>
[-- Attachment #1: Type: text/plain, Size: 1255 bytes --]
In order to make local privilege escalation more harder, hide
kernel addresses in various /proc files against users with
root (or similar) permissions, too.
Common system hardening tools such as lynis recommend this.
The second version of this patch also increments the package number.
Signed-off-by: Peter Müller <peter.mueller(a)ipfire.org>
---
setup/setup.nm | 2 +-
setup/sysctl/kernel-hardening.conf | 2 +-
2 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/setup/setup.nm b/setup/setup.nm
index e79fff10d..0bb936ccb 100644
--- a/setup/setup.nm
+++ b/setup/setup.nm
@@ -5,7 +5,7 @@
name = setup
version = 3.0
-release = 11
+release = 12
arch = noarch
groups = Base Build System/Base
diff --git a/setup/sysctl/kernel-hardening.conf b/setup/sysctl/kernel-hardening.conf
index 6751bbef6..9bb6e9f45 100644
--- a/setup/sysctl/kernel-hardening.conf
+++ b/setup/sysctl/kernel-hardening.conf
@@ -1,5 +1,5 @@
# Try to keep kernel address exposures out of various /proc files (kallsyms, modules, etc).
-kernel.kptr_restrict = 1
+kernel.kptr_restrict = 2
# Avoid kernel memory address exposures via dmesg.
kernel.dmesg_restrict = 1
--
2.16.4
prev parent reply other threads:[~2019-01-21 20:43 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-20 17:03 [PATCH] " Peter Müller
2019-01-21 10:17 ` Michael Tremer
2019-01-21 20:43 ` Peter Müller [this message]
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=cb91cffd-10e2-c075-ec92-90fa8290eb71@link38.eu \
--to=peter.mueller@link38.eu \
--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