From: "Serge E. Hallyn" <serge@hallyn.com>
To: "ℰ𝓃𝓏ℴ ℱ𝓊𝓀ℯ" <milesonerd@outlook.com>
Cc: "linux-security-module@vger.kernel.org"
<linux-security-module@vger.kernel.org>
Subject: Re: [PATCH 1/3] security: add Lilium - Linux Integrity Lock-In User Module
Date: Sat, 31 May 2025 17:37:22 -0500 [thread overview]
Message-ID: <20250531223722.GA84941@mail.hallyn.com> (raw)
In-Reply-To: <CPUP152MB625985A52C6370FD04970507B060A@CPUP152MB6259.LAMP152.PROD.OUTLOOK.COM>
On Sat, May 31, 2025 at 01:19:27PM +0000, ℰ𝓃𝓏ℴ ℱ𝓊𝓀ℯ wrote:
> This patch adds the Lilium (Linux Integrity Lock-In User Module) security module that blocks ptrace, mmap/mprotect with PROT_EXEC, kexec_load, clone and unshar, delete_module, init_module, open and openat, and ioctl, with modular configuration via sysfs.
1. Please send your patches as inline text, one patch per email
2. Your MAINTAINERS patch has the whole file, not a patch
3. The other patches actually lack the contents of the files you are adding.
-serge
next prev parent reply other threads:[~2025-05-31 22:42 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-31 13:19 [PATCH 1/3] security: add Lilium - Linux Integrity Lock-In User Module ℰ𝓃𝓏ℴ ℱ𝓊𝓀ℯ
2025-05-31 22:37 ` Serge E. Hallyn [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-06-01 1:04 ℰ𝓃𝓏ℴ ℱ𝓊𝓀ℯ
2025-06-01 10:13 ` Simon Thoby
2025-06-01 18:18 ` Casey Schaufler
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=20250531223722.GA84941@mail.hallyn.com \
--to=serge@hallyn.com \
--cc=linux-security-module@vger.kernel.org \
--cc=milesonerd@outlook.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 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).