All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Günther Noack" <gnoack3000@gmail.com>
To: Justin Suess <utilityemal77@gmail.com>
Cc: demiobenour@gmail.com, fahimitahera@gmail.com, hi@alyssa.is,
	ivanov.mikhail1@huawei-partners.com, jannh@google.com,
	konstantin.meskhidze@huawei.com,
	linux-security-module@vger.kernel.org, m@maowtm.org,
	matthieu@buffet.re, mic@digikod.net, paul@paul-moore.com,
	samasth.norway.ananda@oracle.com
Subject: Re: [RFC PATCH 3/5] samples/landlock: Add support for LANDLOCK_ACCESS_FS_CONNECT_UNIX
Date: Sat, 10 Jan 2026 16:05:18 +0100	[thread overview]
Message-ID: <20260110.853ac55cf90b@gnoack.org> (raw)
In-Reply-To: <20260101193009.4005972-1-utilityemal77@gmail.com>

Hello!

On Thu, Jan 01, 2026 at 02:30:06PM -0500, Justin Suess wrote:
> Allow users to separately specify unix socket rights,
> document the variable, and make the right optional.
> 
> Signed-off-by: Justin Suess <utilityemal77@gmail.com>
> Cc: Günther Noack <gnoack3000@gmail.com>

FYI, I ended up not applying this on V2.

I am unconvinced whether further separating the groups of access
rights is a good idea for the sandboxer.  This is just sample code to
be used as reference, so it is good to keep it simple.  I feel that
giving it more granular control over access rights does not help
readers to understand it much further?

It is true though that it would make sense to have this feature in
more production-grade tools. 👍

–Günther

  parent reply	other threads:[~2026-01-10 15:05 UTC|newest]

Thread overview: 38+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-01-01 13:40 [RFC PATCH 0/5] landlock: Pathname-based UNIX connect() control Günther Noack
2026-01-01 13:40 ` [RFC PATCH 1/5] landlock/selftests: add a missing close(srv_fd) call Günther Noack
2026-01-09 10:41   ` Mickaël Salaün
2026-01-09 10:49     ` Mickaël Salaün
2026-01-10 10:37       ` Günther Noack
2026-01-12 16:04         ` Mickaël Salaün
2026-01-01 13:40 ` [RFC PATCH 2/5] landlock: Control connections to pathname UNIX sockets by path Günther Noack
2026-01-01 13:41 ` [RFC PATCH 3/5] samples/landlock: Add support for LANDLOCK_ACCESS_FS_CONNECT_UNIX Günther Noack
2026-01-01 19:30   ` Justin Suess
2026-01-01 22:07     ` Tingmao Wang
2026-01-01 22:11       ` Demi Marie Obenour
2026-01-01 22:19         ` Tingmao Wang
2026-01-01 22:36           ` Demi Marie Obenour
2026-01-01 22:38           ` Justin Suess
2026-01-01 22:39             ` Demi Marie Obenour
2026-01-02  9:53               ` Günther Noack
2026-01-08 12:12                 ` Mickaël Salaün
2026-01-10 15:05     ` Günther Noack [this message]
2026-01-01 13:41 ` [RFC PATCH 4/5] landlock/selftests: test LANDLOCK_ACCESS_FS_CONNECT_UNIX Günther Noack
2026-01-01 13:41 ` [RFC PATCH 5/5] landlock: Document LANDLOCK_ACCESS_FS_UNIX_CONNECT Günther Noack
2026-01-01 22:14 ` [RFC PATCH 0/5] landlock: Pathname-based UNIX connect() control Demi Marie Obenour
2026-01-01 22:34   ` Tingmao Wang
2026-01-01 22:44     ` Demi Marie Obenour
2026-01-02 10:16       ` Günther Noack
2026-01-02 10:25         ` Günther Noack
2026-01-08 11:14           ` Mickaël Salaün
2026-01-02 10:27         ` Demi Marie Obenour
2026-01-02 10:50           ` Günther Noack
2026-01-02 18:37             ` Demi Marie Obenour
2026-01-08 11:14               ` Mickaël Salaün
2026-01-09 11:33                 ` Demi Marie Obenour
2026-01-09 15:25                   ` Mickaël Salaün
2026-01-09 21:02                     ` Demi Marie Obenour
2026-01-12 16:05                       ` Mickaël Salaün
2026-01-09 10:37 ` Mickaël Salaün
2026-01-09 14:41   ` Günther Noack
2026-01-09 15:20     ` Mickaël Salaün
2026-01-11 10:15       ` Günther Noack

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=20260110.853ac55cf90b@gnoack.org \
    --to=gnoack3000@gmail.com \
    --cc=demiobenour@gmail.com \
    --cc=fahimitahera@gmail.com \
    --cc=hi@alyssa.is \
    --cc=ivanov.mikhail1@huawei-partners.com \
    --cc=jannh@google.com \
    --cc=konstantin.meskhidze@huawei.com \
    --cc=linux-security-module@vger.kernel.org \
    --cc=m@maowtm.org \
    --cc=matthieu@buffet.re \
    --cc=mic@digikod.net \
    --cc=paul@paul-moore.com \
    --cc=samasth.norway.ananda@oracle.com \
    --cc=utilityemal77@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.