From: Francis Laniel <flaniel@linux.microsoft.com>
To: linux-security-module@vger.kernel.org
Cc: Casey Schaufler <casey@schaufler-ca.com>,
Eric Biederman <ebiederm@xmission.com>,
Francis Laniel <flaniel@linux.microsoft.com>,
Serge Hallyn <serge@hallyn.com>, James Morris <jmorris@namei.org>,
linux-kernel@vger.kernel.org (open list)
Subject: [RFC PATCH v4 2/2] security/inode.c: Add capabilities file.
Date: Mon, 25 Jul 2022 14:41:23 +0200 [thread overview]
Message-ID: <20220725124123.12975-3-flaniel@linux.microsoft.com> (raw)
In-Reply-To: <20220725124123.12975-1-flaniel@linux.microsoft.com>
This new read-only file prints the capabilities values with their names:
cat /sys/kernel/security/capabilities
0 CAP_CHOWN
1 CAP_DAC_OVERRIDE
...
40 CAP_CHECKPOINT_RESTORE
Acked-by: Casey Schaufler <casey@schaufler-ca.com>
Signed-off-by: Francis Laniel <flaniel@linux.microsoft.com>
---
security/inode.c | 16 ++++++++++++++++
1 file changed, 16 insertions(+)
diff --git a/security/inode.c b/security/inode.c
index 6c326939750d..6da87ae5a8d6 100644
--- a/security/inode.c
+++ b/security/inode.c
@@ -21,6 +21,7 @@
#include <linux/security.h>
#include <linux/lsm_hooks.h>
#include <linux/magic.h>
+#include <linux/capability.h>
static struct vfsmount *mount;
static int mount_count;
@@ -328,6 +329,19 @@ static const struct file_operations lsm_ops = {
};
#endif
+static struct dentry *capabilities_dentry;
+static ssize_t capabilities_read(struct file *unused, char __user *buf,
+ size_t count, loff_t *ppos)
+{
+ return simple_read_from_buffer(buf, count, ppos, cap_string,
+ strlen(cap_string));
+}
+
+static const struct file_operations capabilities_ops = {
+ .read = capabilities_read,
+ .llseek = generic_file_llseek,
+};
+
static int __init securityfs_init(void)
{
int retval;
@@ -345,6 +359,8 @@ static int __init securityfs_init(void)
lsm_dentry = securityfs_create_file("lsm", 0444, NULL, NULL,
&lsm_ops);
#endif
+ capabilities_dentry = securityfs_create_file("capabilities", 0444, NULL,
+ NULL, &capabilities_ops);
return 0;
}
core_initcall(securityfs_init);
--
2.25.1
next prev parent reply other threads:[~2022-07-25 12:42 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-25 12:41 [RFC PATCH v4 0/2] Add capabilities file to securityfs Francis Laniel
2022-07-25 12:41 ` [RFC PATCH v4 1/2] capability: Add cap_string Francis Laniel
2022-07-25 12:41 ` Francis Laniel [this message]
2022-08-16 21:59 ` [RFC PATCH v4 0/2] Add capabilities file to securityfs Paul Moore
2022-08-17 11:53 ` Francis Laniel
2022-08-17 14:52 ` Paul Moore
2022-08-17 15:49 ` Casey Schaufler
2022-08-17 16:10 ` Paul Moore
2022-08-17 16:19 ` Serge E. Hallyn
2022-08-17 16:22 ` Paul Moore
2022-08-17 16:49 ` Casey Schaufler
2022-08-17 17:19 ` Paul Moore
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=20220725124123.12975-3-flaniel@linux.microsoft.com \
--to=flaniel@linux.microsoft.com \
--cc=casey@schaufler-ca.com \
--cc=ebiederm@xmission.com \
--cc=jmorris@namei.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=serge@hallyn.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.