From: Michael Tremer <michael.tremer@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: [PATCH] hide kernel addresses in /proc against privileged users
Date: Mon, 21 Jan 2019 10:17:42 +0000 [thread overview]
Message-ID: <B2B43E94-7188-46F9-AD19-5D2F1E1D9EC6@ipfire.org> (raw)
In-Reply-To: <015ae288-bd5a-15c1-151a-3189d769a984@link38.eu>
[-- Attachment #1: Type: text/plain, Size: 1061 bytes --]
Hello,
Please increment the release number of this package.
Best,
-Michael
> On 20 Jan 2019, at 17:03, Peter Müller <peter.mueller(a)link38.eu> wrote:
>
> 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.
>
> Signed-off-by: Peter Müller <peter.mueller(a)ipfire.org>
> ---
> setup/sysctl/kernel-hardening.conf | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> 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
next prev parent reply other threads:[~2019-01-21 10:17 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-20 17:03 Peter Müller
2019-01-21 10:17 ` Michael Tremer [this message]
2019-01-21 20:43 ` [PATCH v2] " Peter Müller
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=B2B43E94-7188-46F9-AD19-5D2F1E1D9EC6@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