From: Vitaly Chikunov <vt@altlinux.org>
To: "Mickaël Salaün" <mic@digikod.net>, landlock@lists.linux.dev
Subject: R/O protection for lower level dirs
Date: Mon, 1 Apr 2024 19:06:14 +0300 [thread overview]
Message-ID: <20240401160614.32py2wrijdp5yots@altlinux.org> (raw)
Hi,
I want to ensure that some deeper directory is write protected (as a non
security measure but so that some post-install processing do not
accidentally touch installed files). Is there a way to achieve this
with Landlock?
For example, if we do R/W access to / (root tree is already protected
enough with DAC) and then R/O access to /home we still get full R/W access
everywhere and /home seems not restricted. Also, Landlock does not warn for
such configuration, silently accepting it as valid.
Practical example:
~$ LL_FS_RW=/ LL_FS_RO=/home sandboxer touch a
Executing the sandboxed command...
~$ ls -l a
-rw-r--r-- 1 vt vt 0 Apr 1 15:53 a
Thanks,
next reply other threads:[~2024-04-01 16:06 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-01 16:06 Vitaly Chikunov [this message]
2024-04-02 9:11 ` R/O protection for lower level dirs Mickaël Salaün
2024-04-03 15:20 ` Vitaly Chikunov
2024-04-03 16:57 ` Mickaël Salaün
2024-04-05 16:04 ` Vitaly Chikunov
2024-04-06 17:19 ` Mickaël Salaün
2024-04-04 8:03 ` Simon de Vlieger
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=20240401160614.32py2wrijdp5yots@altlinux.org \
--to=vt@altlinux.org \
--cc=landlock@lists.linux.dev \
--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 read-only IMAP folder(s) and NNTP newsgroup(s).