[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <3cb894d4-049f-aa25-4450-d1df36a1b92e@gmail.com>
Date: Sat, 24 Oct 2020 14:34:06 +0300
From: Topi Miettinen <toiwoton@...il.com>
To: Salvatore Mesoraca <s.mesoraca16@...il.com>
Cc: Kees Cook <keescook@...omium.org>, Szabolcs Nagy <szabolcs.nagy@....com>,
Jeremy Linton <jeremy.linton@....com>,
"linux-arm-kernel@...ts.infradead.org"
<linux-arm-kernel@...ts.infradead.org>, libc-alpha@...rceware.org,
systemd-devel@...ts.freedesktop.org,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
Mark Rutland <mark.rutland@....com>, Mark Brown <broonie@...nel.org>,
Dave Martin <dave.martin@....com>, Catalin Marinas
<Catalin.Marinas@....com>, Will Deacon <will.deacon@....com>,
Kernel Hardening <kernel-hardening@...ts.openwall.com>,
linux-hardening@...r.kernel.org
Subject: Re: BTI interaction between seccomp filters in systemd and glibc
mprotect calls, causing service failures
On 23.10.2020 20.52, Salvatore Mesoraca wrote:
> Hi,
>
> On Thu, 22 Oct 2020 at 23:24, Topi Miettinen <toiwoton@...il.com> wrote:
>> SARA looks interesting. What is missing is a prctl() to enable all W^X
>> protections irrevocably for the current process, then systemd could
>> enable it for services with MemoryDenyWriteExecute=yes.
>
> SARA actually has a procattr[0] interface to do just that.
> There is also a library[1] to help using it.
That means that /proc has to be available and writable at that point, so
setting up procattrs has to be done before mount namespaces are set up.
In general, it would be nice for sandboxing facilities in kernel if
there would be a way to start enforcing restrictions only at next
execve(), like setexeccon() for SELinux and aa_change_onexec() for
AppArmor. Otherwise the exact order of setting up various sandboxing
options can be very tricky to arrange correctly, since each option may
have a subtle effect to the sandboxing features enabled later. In case
of SARA, the operations done between shuffling the mount namespace and
before execve() shouldn't be affected so it isn't important. Even if it
did (a new sandboxing feature in the future would need trampolines or
JIT code generation), maybe the procattr file could be opened early but
it could be written closer to execve().
-Topi
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.
