From: Jay Freyensee <why2jjj.linux@gmail.com>
To: landlock@lists.linux.dev
Subject: self protect process with landlock to getting killed
Date: Tue, 27 Jun 2023 09:14:42 -0700 [thread overview]
Message-ID: <480a4459-dcfe-e5ce-bce8-6fc59cb89b9e@gmail.com> (raw)
Hi I had a question for someone. Is there a way to protect a landlocked
process from being killed by a non-landlock process? Does that
protection include root protection and root not being able to kill that
landlocked process?
What about is there a way to protect the directory the landlock process
sits in from being tampered/written-to by a non-landlock process?
I came up with the question from reading this comment in the kernel docs:
"Once a thread is landlocked, there is no way to remove its security
policy; only adding more restrictions is allowed."
I believe you can get this protection through SELinux I was just curious
if the landlocked gave you that as well; SELinux can be confusing to
work with.
Thank you,
Jay
next reply other threads:[~2023-06-27 16:14 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-27 16:14 Jay Freyensee [this message]
2023-06-28 15:04 ` self protect process with landlock to getting killed Mickaël Salaün
2023-06-28 15:20 ` Jay Freyensee
2023-06-28 17:38 ` 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=480a4459-dcfe-e5ce-bce8-6fc59cb89b9e@gmail.com \
--to=why2jjj.linux@gmail.com \
--cc=landlock@lists.linux.dev \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).