|
Message-ID: <20240709.chait2ahKeos@digikod.net> Date: Tue, 9 Jul 2024 22:42:45 +0200 From: Mickaël Salaün <mic@...ikod.net> To: Mimi Zohar <zohar@...ux.ibm.com> Cc: Al Viro <viro@...iv.linux.org.uk>, Christian Brauner <brauner@...nel.org>, Kees Cook <keescook@...omium.org>, Linus Torvalds <torvalds@...ux-foundation.org>, Paul Moore <paul@...l-moore.com>, Theodore Ts'o <tytso@....edu>, Alejandro Colomar <alx@...nel.org>, Aleksa Sarai <cyphar@...har.com>, Andrew Morton <akpm@...ux-foundation.org>, Andy Lutomirski <luto@...nel.org>, Arnd Bergmann <arnd@...db.de>, Casey Schaufler <casey@...aufler-ca.com>, Christian Heimes <christian@...hon.org>, Dmitry Vyukov <dvyukov@...gle.com>, Eric Biggers <ebiggers@...nel.org>, Eric Chiang <ericchiang@...gle.com>, Fan Wu <wufan@...ux.microsoft.com>, Florian Weimer <fweimer@...hat.com>, Geert Uytterhoeven <geert@...ux-m68k.org>, James Morris <jamorris@...ux.microsoft.com>, Jan Kara <jack@...e.cz>, Jann Horn <jannh@...gle.com>, Jeff Xu <jeffxu@...gle.com>, Jonathan Corbet <corbet@....net>, Jordan R Abrahams <ajordanr@...gle.com>, Lakshmi Ramasubramanian <nramas@...ux.microsoft.com>, Luca Boccassi <bluca@...ian.org>, Luis Chamberlain <mcgrof@...nel.org>, "Madhavan T . Venkataraman" <madvenka@...ux.microsoft.com>, Matt Bobrowski <mattbobrowski@...gle.com>, Matthew Garrett <mjg59@...f.ucam.org>, Matthew Wilcox <willy@...radead.org>, Miklos Szeredi <mszeredi@...hat.com>, Nicolas Bouchinet <nicolas.bouchinet@....gouv.fr>, Scott Shell <scottsh@...rosoft.com>, Shuah Khan <shuah@...nel.org>, Stephen Rothwell <sfr@...b.auug.org.au>, Steve Dower <steve.dower@...hon.org>, Steve Grubb <sgrubb@...hat.com>, Thibaut Sautereau <thibaut.sautereau@....gouv.fr>, Vincent Strubel <vincent.strubel@....gouv.fr>, Xiaoming Ni <nixiaoming@...wei.com>, Yin Fengwei <fengwei.yin@...el.com>, kernel-hardening@...ts.openwall.com, linux-api@...r.kernel.org, linux-fsdevel@...r.kernel.org, linux-integrity@...r.kernel.org, linux-kernel@...r.kernel.org, linux-security-module@...r.kernel.org Subject: Re: [RFC PATCH v19 5/5] samples/should-exec: Add set-should-exec On Mon, Jul 08, 2024 at 03:40:42PM -0400, Mimi Zohar wrote: > Hi Mickaël, > > On Thu, 2024-07-04 at 21:01 +0200, Mickaël Salaün wrote: > > Add a simple tool to set SECBIT_SHOULD_EXEC_CHECK, > > SECBIT_SHOULD_EXEC_RESTRICT, and their lock counterparts before > > executing a command. This should be useful to easily test against > > script interpreters. > > The print_usage() provides the calling syntax. Could you provide an example of > how to use it and what to expect? To set SECBIT_SHOULD_EXEC_CHECK, SECBIT_SHOULD_EXEC_RESTRICT, and lock them on a new shell (session) we can use this: ./set-should-exec -crl -- bash -i This would have no impact unless Bash, ld.so, or one of its child code is patched to restrict execution (e.g. with execveat+AT_CHECK check). Script interpreters and dynamic linkers need to be patch on a secure sysetm. Steve is enlightening Python, and we'll need more similar changes for common user space code. This can be an incremental work and only enforced on some user sessions or containers for instance. > > thanks, > > Mimi > >
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.