Skip to content

RFC Use socket's Landlock domain

Mickaël Salaün linux-security-module lkml stable 1 version In review

Get series with b4
b4 am [email protected]

Versions newest first

  1. v1 RFC Latest3 patches 2 repliesIn review

Patches in v1 No applies recorded yet

#Subject and filesSizeRepliesApplied
1/3landlock: Use socket's domain instead of current's domainsecurity/landlock/net.c+11 -110 replies
2/3selftests/landlock: Add test for socket's domaintools/testing/selftests/landlock/net_test.c+29 -00 replies
3/3landlock: Document network restrictions tied to socketsDocumentation/userspace-api/landlock.rst+3 -10 replies

Reviews trailers per patch

No Reviewed-by, Acked-by or Tested-by trailers for v1 yet.

Read the v1 thread

Cover letter [RFC PATCH v1 0/3] Use socket's Landlock domain

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

Signature · 1 line
2.45.2