From: crtxcr <crtxcr@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: linux5.15+: Add landlock to CONFIG_LSM
Date: Thu, 29 Dec 2022 08:34:54 +0100 [thread overview]
Message-ID: <20221229073454.uPmkiEVUV54ae7eWutpWFYrHlIRQj2JWVNvm93EdGi0@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-41337@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 915 bytes --]
New comment by crtxcr on void-packages repository
https://github.com/void-linux/void-packages/pull/41337#issuecomment-1367126001
Comment:
@sgn Yes, @paper42 said that much already and I replied why I believe it should be enabled.
To expand on that, I really think regarding landlock the better question is why not to enable it, given it operates on a per-process basis. It doesn't do anything if a process doesn't use it. For those who do, it can serve as a useful tool to create sandboxes or mitigate the effects of exploited vulnerabilities. If, like currently, it simply off a process that would otherwise utilize it might not benefit from it.
It can be assumed most users will not add it to lsm= boot parameters, so they won't benefit from it.
It's also on in Arch, Gentoo, Fedora and Ubuntu. If it was a problematic module it would have been noticed by now. So why shouldn't void enable it too?
next prev parent reply other threads:[~2022-12-29 7:34 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-28 23:09 [PR PATCH] " crtxcr
2022-12-28 23:14 ` paper42
2022-12-28 23:40 ` crtxcr
2022-12-29 1:42 ` sgn
2022-12-29 1:44 ` sgn
2022-12-29 7:34 ` crtxcr [this message]
2022-12-29 7:44 ` [PR PATCH] [Merged]: " sgn
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=20221229073454.uPmkiEVUV54ae7eWutpWFYrHlIRQj2JWVNvm93EdGi0@z \
--to=crtxcr@users.noreply.github.com \
--cc=ml@inbox.vuxu.org \
/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).