From: Tahera Fahimi <fahimitahera@gmail.com>
To: "Mickaël Salaün" <mic@digikod.net>
Cc: outreachy@lists.linux.dev, gnoack@google.com,
paul@paul-moore.com, jmorris@namei.org, serge@hallyn.com,
linux-security-module@vger.kernel.org,
linux-kernel@vger.kernel.org, bjorn3_gh@protonmail.com,
jannh@google.com, netdev@vger.kernel.org
Subject: Re: [PATCH v9 0/5] Landlock: Add abstract unix socket connect restriction
Date: Mon, 19 Aug 2024 14:16:04 -0600 [thread overview]
Message-ID: <ZsOoBPpNZ+8KXKus@tahera-OptiPlex-5000> (raw)
In-Reply-To: <20240819.Gie1thiegeek@digikod.net>
On Mon, Aug 19, 2024 at 09:58:27PM +0200, Mickaël Salaün wrote:
> There are still some issues (mainly with tests) but overall the kernel
> part looks good! I pushed this patch series to the -next branch. I'll
> update with the next versions of this series.
Thank you :)
> I'll do the same with the next signal scoping patch series once the
> lifetime issue that Jann reported is fixed.
I have already applied those changes, but still need to add a test case
for file_send_sigiotask()
> On Wed, Aug 14, 2024 at 12:22:18AM -0600, Tahera Fahimi wrote:
> > This patch series adds scoping mechanism for abstract unix sockets.
> > Closes: https://github.com/landlock-lsm/linux/issues/7
> >
> > Problem
> > =======
> >
> > Abstract unix sockets are used for local inter-process communications
> > independent of the filesystem. Currently, a sandboxed process can
> > connect to a socket outside of the sandboxed environment, since Landlock
> > has no restriction for connecting to an abstract socket address(see more
> > details in [1,2]). Access to such sockets for a sandboxed process should
> > be scoped the same way ptrace is limited.
> >
> > [1] https://lore.kernel.org/all/20231023.ahphah4Wii4v@digikod.net/
> > [2] https://lore.kernel.org/all/20231102.MaeWaepav8nu@digikod.net/
> >
> > Solution
> > ========
> >
> > To solve this issue, we extend the user space interface by adding a new
> > "scoped" field to Landlock ruleset attribute structure. This field can
> > contains different rights to restrict different functionalities. For
> > abstract unix sockets, we introduce
> > "LANDLOCK_SCOPED_ABSTRACT_UNIX_SOCKET" field to specify that a ruleset
> > will deny any connection from within the sandbox domain to its parent
> > (i.e. any parent sandbox or non-sandbox processes).
> >
> > Example
> > =======
> >
> > Starting a listening socket with socat(1):
> > socat abstract-listen:mysocket -
> >
> > Starting a sandboxed shell from $HOME with samples/landlock/sandboxer:
> > LL_FS_RO=/ LL_FS_RW=. LL_SCOPED="a" ./sandboxer /bin/bash
> >
> > If we try to connect to the listening socket, the connection would be
> > refused.
> > socat - abstract-connect:mysocket --> fails
> >
> >
> > Notes of Implementation
> > =======================
> >
> > * Using the "scoped" field provides enough compatibility and flexibility
> > to extend the scoping mechanism for other IPCs(e.g. signals).
> >
> > * To access the domain of a socket, we use its credentials of the file's FD
> > which point to the credentials of the process that created the socket.
> > (see more details in [3]). Cases where the process using the socket has
> > a different domain than the process created it are covered in the
> > unix_sock_special_cases test.
> >
> > [3]https://lore.kernel.org/all/20240611.Pi8Iph7ootae@digikod.net/
> >
> > Previous Versions
> > =================
> > v8: https://lore.kernel.org/all/cover.1722570749.git.fahimitahera@gmail.com/
> > v7: https://lore.kernel.org/all/cover.1721269836.git.fahimitahera@gmail.com/
> > v6: https://lore.kernel.org/all/Zn32CYZiu7pY+rdI@tahera-OptiPlex-5000/
> > and https://lore.kernel.org/all/Zn32KKIJrY7Zi51K@tahera-OptiPlex-5000/
> > v5: https://lore.kernel.org/all/ZnSZnhGBiprI6FRk@tahera-OptiPlex-5000/
> > v4: https://lore.kernel.org/all/ZnNcE3ph2SWi1qmd@tahera-OptiPlex-5000/
> > v3: https://lore.kernel.org/all/ZmJJ7lZdQuQop7e5@tahera-OptiPlex-5000/
> > v2: https://lore.kernel.org/all/ZgX5TRTrSDPrJFfF@tahera-OptiPlex-5000/
> > v1: https://lore.kernel.org/all/ZgXN5fi6A1YQKiAQ@tahera-OptiPlex-5000/
> >
> > Tahera Fahimi (5):
> > Landlock: Add abstract unix socket connect restriction
> > selftests/Landlock: Abstract unix socket restriction tests
> > selftests/Landlock: Adding pathname Unix socket tests
> > sample/Landlock: Support abstract unix socket restriction
> > Landlock: Document LANDLOCK_SCOPED_ABSTRACT_UNIX_SOCKET and ABI
> > versioning
> >
> > Documentation/userspace-api/landlock.rst | 33 +-
> > include/uapi/linux/landlock.h | 27 +
> > samples/landlock/sandboxer.c | 58 +-
> > security/landlock/limits.h | 3 +
> > security/landlock/ruleset.c | 7 +-
> > security/landlock/ruleset.h | 23 +-
> > security/landlock/syscalls.c | 17 +-
> > security/landlock/task.c | 129 ++
> > tools/testing/selftests/landlock/base_test.c | 2 +-
> > tools/testing/selftests/landlock/common.h | 38 +
> > tools/testing/selftests/landlock/net_test.c | 31 +-
> > .../landlock/scoped_abstract_unix_test.c | 1146 +++++++++++++++++
> > 12 files changed, 1469 insertions(+), 45 deletions(-)
> > create mode 100644 tools/testing/selftests/landlock/scoped_abstract_unix_test.c
> >
> > --
> > 2.34.1
> >
> >
prev parent reply other threads:[~2024-08-19 20:16 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-14 6:22 [PATCH v9 0/5] Landlock: Add abstract unix socket connect restriction Tahera Fahimi
2024-08-14 6:22 ` [PATCH v9 1/5] " Tahera Fahimi
2024-08-16 21:19 ` Mickaël Salaün
2024-08-19 15:37 ` Mickaël Salaün
2024-08-19 22:20 ` Tahera Fahimi
2024-08-20 15:56 ` Mickaël Salaün
2024-08-19 19:35 ` Mickaël Salaün
2024-08-14 6:22 ` [PATCH v9 2/5] selftests/Landlock: Abstract unix socket restriction tests Tahera Fahimi
2024-08-16 21:23 ` Mickaël Salaün
2024-08-16 23:08 ` Tahera Fahimi
2024-08-19 15:38 ` Mickaël Salaün
2024-08-19 15:42 ` Mickaël Salaün
2024-08-19 19:55 ` Tahera Fahimi
2024-08-14 6:22 ` [PATCH v9 3/5] selftests/Landlock: Adding pathname Unix socket tests Tahera Fahimi
2024-08-19 19:47 ` Mickaël Salaün
2024-08-14 6:22 ` [PATCH v9 4/5] sample/Landlock: Support abstract unix socket restriction Tahera Fahimi
2024-08-19 19:47 ` Mickaël Salaün
2024-08-14 6:22 ` [PATCH v9 5/5] Landlock: Document LANDLOCK_SCOPED_ABSTRACT_UNIX_SOCKET and ABI versioning Tahera Fahimi
2024-08-19 19:49 ` Mickaël Salaün
2024-08-19 19:58 ` [PATCH v9 0/5] Landlock: Add abstract unix socket connect restriction Mickaël Salaün
2024-08-19 20:16 ` Tahera Fahimi [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=ZsOoBPpNZ+8KXKus@tahera-OptiPlex-5000 \
--to=fahimitahera@gmail.com \
--cc=bjorn3_gh@protonmail.com \
--cc=gnoack@google.com \
--cc=jannh@google.com \
--cc=jmorris@namei.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=mic@digikod.net \
--cc=netdev@vger.kernel.org \
--cc=outreachy@lists.linux.dev \
--cc=paul@paul-moore.com \
--cc=serge@hallyn.com \
/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