[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <fbf37518-328d-c08c-7140-5d09d7a2674f@redhat.com>
Date: Fri, 5 May 2023 09:35:59 +0200
From: David Hildenbrand <david@...hat.com>
To: Michael McCracken <michael.mccracken@...il.com>,
linux-kernel@...r.kernel.org
Cc: kernel-hardening@...ts.openwall.com, serge@...lyn.com, tycho@...ho.pizza,
Luis Chamberlain <mcgrof@...nel.org>, Kees Cook <keescook@...omium.org>,
Iurii Zaikin <yzaikin@...gle.com>, Andrew Morton
<akpm@...ux-foundation.org>, linux-fsdevel@...r.kernel.org,
linux-mm@...ck.org
Subject: Re: [PATCH] sysctl: add config to make randomize_va_space RO
On 04.05.23 23:30, Michael McCracken wrote:
> Add config RO_RANDMAP_SYSCTL to set the mode of the randomize_va_space
> sysctl to 0444 to disallow all runtime changes. This will prevent
> accidental changing of this value by a root service.
>
> The config is disabled by default to avoid surprises.
Can you elaborate why we care about "accidental changing of this value
by a root service"?
We cannot really stop root from doing a lot of stupid things (e.g.,
erase the root fs), so why do we particularly care here?
--
Thanks,
David / dhildenb
Powered by blists - more mailing lists
Confused about mailing lists and their use?
Read about mailing lists on Wikipedia
and check out these
guidelines on proper formatting of your messages.
