| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Message-ID: <20250304222304.214704-2-paul@paul-moore.com> Date: Tue, 4 Mar 2025 17:23:05 -0500 From: Paul Moore <paul@...l-moore.com> To: linux-kernel@...r.kernel.org, linux-security-module@...r.kernel.org Subject: [RFC PATCH] MAINTAINERS: add an explicit credentials entry The lack of an explicit credential (kernel/cred.c) entry has caused confusion in the past among new, and not-so-new developers, about where to send credential patches for discussion and merging. Those patches that are sent can often rot on the mailing lists for months as there is no clear maintainer tasked with reviewing and merging patches. I'm volunteering for the cred maintainer role to try and reduce the confusion and help cred patches find their way up to Linus' tree. As there generally aren't a lot of cred patches I'll start with simply folding them into the LSM tree, but if this changes I'll setup a dedicated cred tree. Signed-off-by: Paul Moore <paul@...l-moore.com> --- MAINTAINERS | 8 ++++++++ 1 file changed, 8 insertions(+) diff --git a/MAINTAINERS b/MAINTAINERS index 896a307fa065..68e4656c15ea 100644 --- a/MAINTAINERS +++ b/MAINTAINERS @@ -6139,6 +6139,14 @@ L: linux-input@...r.kernel.org S: Maintained F: drivers/hid/hid-creative-sb0540.c +CREDENTIALS +M: Paul Moore <paul@...l-moore.com> +L: linux-security-module@...r.kernel.org +S: Supported +T: git https://git.kernel.org/pub/scm/linux/kernel/git/pcmoore/lsm.git +F: include/linux/cred.h +F: kernel/cred.c + INTEL CRPS COMMON REDUNDANT PSU DRIVER M: Ninad Palsule <ninad@...ux.ibm.com> L: linux-hwmon@...r.kernel.org -- 2.48.1
Powered by blists - more mailing lists