From: Matthieu Buffet <matthieu@buffet.re>
To: "Mickaël Salaün" <mic@digikod.net>
Cc: "Günther Noack" <gnoack@google.com>,
"Konstantin Meskhidze" <konstantin.meskhidze@huawei.com>,
"Ivanov Mikhail" <ivanov.mikhail1@huawei-partners.com>,
linux-security-module@vger.kernel.org,
linux-kernel@vger.kernel.org,
"Matthieu Buffet" <matthieu@buffet.re>
Subject: [PATCH v2 3/3] samples/landlock: Clarify option parsing behaviour
Date: Thu, 3 Oct 2024 02:50:42 +0200 [thread overview]
Message-ID: <20241003005042.258991-3-matthieu@buffet.re> (raw)
In-Reply-To: <20241003005042.258991-1-matthieu@buffet.re>
- Clarify which environment variables are optional, which ones are
mandatory
- Clarify the difference between unset variables and empty ones
Signed-off-by: Matthieu Buffet <matthieu@buffet.re>
---
samples/landlock/sandboxer.c | 22 +++++++++++++---------
1 file changed, 13 insertions(+), 9 deletions(-)
diff --git a/samples/landlock/sandboxer.c b/samples/landlock/sandboxer.c
index f16994d35d9e..a28e4a9c5f87 100644
--- a/samples/landlock/sandboxer.c
+++ b/samples/landlock/sandboxer.c
@@ -298,24 +298,27 @@ static bool check_ruleset_scope(const char *const env_var,
static void print_help(const char *argv0)
{
fprintf(stderr,
- "usage: %s=\"...\" %s=\"...\" %s=\"...\" %s=\"...\" %s=\"...\" %s "
+ "usage: %s=\"...\" %s=\"...\" [other environment variables] %s "
"<cmd> [args]...\n\n",
- ENV_FS_RO_NAME, ENV_FS_RW_NAME, ENV_TCP_BIND_NAME,
- ENV_TCP_CONNECT_NAME, ENV_SCOPED_NAME, argv0);
+ ENV_FS_RO_NAME, ENV_FS_RW_NAME, argv0);
fprintf(stderr,
"Execute a command in a restricted environment.\n\n");
fprintf(stderr,
- "Environment variables containing paths and ports "
- "each separated by a colon:\n");
+ "All environment variables can be multi-valued, with a "
+ "colon delimiter.\n"
+ "\n"
+ "Mandatory settings:\n");
fprintf(stderr,
"* %s: list of paths allowed to be used in a read-only way.\n",
ENV_FS_RO_NAME);
fprintf(stderr,
- "* %s: list of paths allowed to be used in a read-write way.\n\n",
+ "* %s: list of paths allowed to be used in a read-write way.\n",
ENV_FS_RW_NAME);
fprintf(stderr,
- "Environment variables containing ports are optional "
- "and could be skipped.\n");
+ "\n"
+ "Optional settings (when not set, their associated access "
+ "check is always allowed, which is different from an empty "
+ "string which means an empty list)\n");
fprintf(stderr,
"* %s: list of ports allowed to bind (server).\n",
ENV_TCP_BIND_NAME);
@@ -325,7 +328,8 @@ static void print_help(const char *argv0)
fprintf(stderr, "* %s: list of scoped IPCs.\n",
ENV_SCOPED_NAME);
fprintf(stderr,
- "\nexample:\n"
+ "\n"
+ "Example:\n"
"%s=\"${PATH}:/lib:/usr:/proc:/etc:/dev/urandom\" "
"%s=\"/dev/null:/dev/full:/dev/zero:/dev/pts:/tmp\" "
"%s=\"9418\" "
--
2.39.2
next prev parent reply other threads:[~2024-10-03 0:50 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-03 0:50 [PATCH v2 1/3] samples/landlock: Fix port parsing in sandboxer Matthieu Buffet
2024-10-03 0:50 ` [PATCH v2 2/3] samples/landlock: Refactor --help message in function Matthieu Buffet
2024-10-03 15:27 ` Mickaël Salaün
2024-10-03 0:50 ` Matthieu Buffet [this message]
2024-10-03 15:29 ` [PATCH v2 3/3] samples/landlock: Clarify option parsing behaviour 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=20241003005042.258991-3-matthieu@buffet.re \
--to=matthieu@buffet.re \
--cc=gnoack@google.com \
--cc=ivanov.mikhail1@huawei-partners.com \
--cc=konstantin.meskhidze@huawei.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=mic@digikod.net \
/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;
as well as URLs for NNTP newsgroup(s).