From: "Günther Noack" <gnoack@google.com>
To: "Alejandro Colomar" <alx@kernel.org>,
"Mickaël Salaün" <mic@digikod.net>,
"Tahera Fahimi" <fahimitahera@gmail.com>
Cc: "Günther Noack" <gnoack@google.com>,
"Tanya Agarwal" <tanyaagarwal25699@gmail.com>,
linux-security-module@vger.kernel.org, linux-man@vger.kernel.org,
"Daniel Burgener" <dburgener@linux.microsoft.com>
Subject: [PATCH v2 1/3] landlock.7: Update description of Landlock rules
Date: Wed, 26 Feb 2025 22:29:10 +0100 [thread overview]
Message-ID: <20250226212911.34502-2-gnoack@google.com> (raw)
In-Reply-To: <20250226211814.31420-2-gnoack@google.com>
This brings it up to date with the wording in the kernel documentation.
Signed-off-by: Günther Noack <gnoack@google.com>
---
man/man7/landlock.7 | 20 ++++++++++++++++----
1 file changed, 16 insertions(+), 4 deletions(-)
diff --git a/man/man7/landlock.7 b/man/man7/landlock.7
index c6b7272ea..11f76b072 100644
--- a/man/man7/landlock.7
+++ b/man/man7/landlock.7
@@ -39,13 +39,25 @@ the running kernel must support Landlock and
it must be enabled at boot time.
.\"
.SS Landlock rules
-A Landlock rule describes an action on an object.
-An object is currently a file hierarchy,
-and the related filesystem actions are defined with access rights (see
-.BR landlock_add_rule (2)).
+A Landlock rule describes an action on an object
+which the process intends to perform.
A set of rules is aggregated in a ruleset,
which can then restrict the thread enforcing it,
and its future children.
+.P
+The two existing types of rules are:
+.P
+.TP
+.B Filesystem rules
+For these rules, the object is a file hierarchy,
+and the related filesystem actions are defined with
+.IR "filesystem access rights" .
+.TP
+.B Network rules (since ABI v4)
+For these rules, the object is a TCP port,
+and the related actions are defined with
+.IR "network access rights" .
+.BR landlock_add_rule (2)).
.\"
.SS Filesystem actions
These flags enable to restrict a sandboxed process to a
--
2.48.1.711.g2feabab25a-goog
next prev parent reply other threads:[~2025-02-26 21:29 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-26 21:18 [PATCH v2 0/1] landlock: Clarify IPC scoping documentation Günther Noack
2025-02-26 21:18 ` [PATCH v2 1/1] " Günther Noack
2025-02-26 21:29 ` Günther Noack [this message]
2025-02-26 21:40 ` [PATCH v2 1/3] landlock.7: Update description of Landlock rules Günther Noack
2025-02-28 21:31 ` Alejandro Colomar
2025-03-03 15:16 ` Günther Noack
2025-02-26 21:29 ` [PATCH v2 2/3] landlock.7: Move over documentation for ABI version 6 Günther Noack
2025-02-28 21:23 ` Alejandro Colomar
2025-03-03 16:24 ` Günther Noack
2025-03-03 18:30 ` Alejandro Colomar
2025-02-26 21:29 ` [PATCH v2 3/3] landlock.7: Clarify IPC scoping documentation in line with kernel side Günther Noack
2025-02-28 21:37 ` Alejandro Colomar
2025-03-03 16:36 ` 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=20250226212911.34502-2-gnoack@google.com \
--to=gnoack@google.com \
--cc=alx@kernel.org \
--cc=dburgener@linux.microsoft.com \
--cc=fahimitahera@gmail.com \
--cc=linux-man@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=mic@digikod.net \
--cc=tanyaagarwal25699@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.