From: "Mickaël Salaün" <mic@digikod.net>
To: "Günther Noack" <gnoack@google.com>,
"Ivanov Mikhail" <ivanov.mikhail1@huawei-partners.com>,
"Konstantin Meskhidze" <konstantin.meskhidze@huawei.com>,
"Paul Moore" <paul@paul-moore.com>
Cc: "Mickaël Salaün" <mic@digikod.net>,
"Casey Schaufler" <casey@schaufler-ca.com>,
"Jeff Xu" <jeffxu@google.com>,
"Kees Cook" <keescook@chromium.org>,
"Serge E . Hallyn" <serge@hallyn.com>,
"Shervin Oloumi" <enlightened@chromium.org>,
"Tahera Fahimi" <fahimitahera@gmail.com>,
linux-kernel@vger.kernel.org,
linux-security-module@vger.kernel.org
Subject: [RFC PATCH v1 0/3] Use socket's Landlock domain
Date: Fri, 19 Jul 2024 17:06:15 +0200 [thread overview]
Message-ID: <20240719150618.197991-1-mic@digikod.net> (raw)
Hi,
While the current approach works, I think we should change the way
Landlock restricts network actions. Because this feature is relatively
new, we can still fix this inconsistency. In a nutshell, let's follow a
more capability-based model. Please let me know what you think.
Regards,
Mickaël Salaün (3):
landlock: Use socket's domain instead of current's domain
selftests/landlock: Add test for socket's domain
landlock: Document network restrictions tied to sockets
Documentation/userspace-api/landlock.rst | 4 ++-
security/landlock/net.c | 22 ++++++++--------
tools/testing/selftests/landlock/net_test.c | 29 +++++++++++++++++++++
3 files changed, 43 insertions(+), 12 deletions(-)
base-commit: f4b89d8ce5a835afa51404977ee7e3889c2b9722
--
2.45.2
next reply other threads:[~2024-07-19 15:06 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-19 15:06 Mickaël Salaün [this message]
2024-07-19 15:06 ` [RFC PATCH v1 1/3] landlock: Use socket's domain instead of current's domain Mickaël Salaün
2024-07-19 15:06 ` [RFC PATCH v1 2/3] selftests/landlock: Add test for socket's domain Mickaël Salaün
2024-07-19 15:06 ` [RFC PATCH v1 3/3] landlock: Document network restrictions tied to sockets Mickaël Salaün
2024-07-23 13:07 ` [RFC PATCH v1 0/3] Use socket's Landlock domain Günther Noack
2024-07-23 16:50 ` Mickaël Salaün
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=20240719150618.197991-1-mic@digikod.net \
--to=mic@digikod.net \
--cc=casey@schaufler-ca.com \
--cc=enlightened@chromium.org \
--cc=fahimitahera@gmail.com \
--cc=gnoack@google.com \
--cc=ivanov.mikhail1@huawei-partners.com \
--cc=jeffxu@google.com \
--cc=keescook@chromium.org \
--cc=konstantin.meskhidze@huawei.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--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
all inboxes | Powered by JetHome®