From: Jia Zhang <zhang.jia@linux.alibaba.com>
To: Jessica Yu <jeyu@kernel.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH 3/4] module: Support to show the current enforcement policy
Date: Thu, 8 Mar 2018 09:57:02 +0800 [thread overview]
Message-ID: <a4393541-5240-3924-8d29-3449ddf616d8@linux.alibaba.com> (raw)
In-Reply-To: <20180307201408.ssuzsmbatntk67yz@redbean>
On 2018/3/8 上午4:14, Jessica Yu wrote:
> +++ Jia Zhang [01/03/18 17:09 +0800]:
>> /sys/kernel/security/modsign/enforce gives the result of current
>> enforcement policy of loading module.
>>
>> Signed-off-by: Jia Zhang <zhang.jia@linux.alibaba.com>
>
> Why is this being added as part of securityfs? AFAIK that's primarily
> used by LSMs.
The integrity subsystem such as IMA is also located there.
>
> And we already export sig_enforce to sysfs (See
> /sys/module/module/parameters/sig_enforce).
> It already does exactly what your patchset tries to do, it only allows
> for enablement.
I will respond this in V2.
Thanks,
Jia
> Jessica
>
>> ---
>> kernel/module.c | 55
>> +++++++++++++++++++++++++++++++++++++++++++++++++++++++
>> 1 file changed, 55 insertions(+)
>>
>> diff --git a/kernel/module.c b/kernel/module.c
>> index 79825ea..e3c6c8e 100644
>> --- a/kernel/module.c
>> +++ b/kernel/module.c
>> @@ -2794,11 +2794,60 @@ static int module_sig_check(struct load_info
>> *info, int flags)
>>
>> return err;
>> }
>> +
>> +#ifdef CONFIG_SECURITYFS
>> +static ssize_t modsign_enforce_read(struct file *filp, char __user
>> *ubuf,
>> + size_t count, loff_t *offp)
>> +{
>> + char buf[2];
>> +
>> + sprintf(buf, "%d", !!sig_enforce);
>> +
>> + return simple_read_from_buffer(ubuf, count, offp, buf, 1);
>> +}
>> +
>> +static const struct file_operations modsign_enforce_ops = {
>> + .read = modsign_enforce_read,
>> + .llseek = generic_file_llseek,
>> +};
>> +
>> +static int __init securityfs_init(void)
>> +{
>> + struct dentry *modsign_dir;
>> + struct dentry *enforce;
>> +
>> + modsign_dir = securityfs_create_dir("modsign", NULL);
>> + if (IS_ERR(modsign_dir))
>> + return -1;
>> +
>> + enforce = securityfs_create_file("enforce",
>> + S_IRUSR | S_IRGRP, modsign_dir,
>> + NULL, &modsign_enforce_ops);
>> + if (IS_ERR(enforce))
>> + goto out;
>> +
>> + return 0;
>> +out:
>> + securityfs_remove(modsign_dir);
>> +
>> + return -1;
>> +}
>> +#else /* !CONFIG_SECURITYFS */
>> +static int __init securityfs_init(void)
>> +{
>> + return 0;
>> +}
>> +#endif
>> #else /* !CONFIG_MODULE_SIG */
>> static int module_sig_check(struct load_info *info, int flags)
>> {
>> return 0;
>> }
>> +
>> +static int __init securityfs_init(void)
>> +{
>> + return 0;
>> +}
>> #endif /* !CONFIG_MODULE_SIG */
>>
>> /* Sanity checks against invalid binaries, wrong arch, weird elf
>> version. */
>> @@ -4395,8 +4444,14 @@ void module_layout(struct module *mod,
>>
>> static int __init initialize_module(void)
>> {
>> + int ret;
>> +
>> proc_modules_init();
>>
>> + ret = securityfs_init();
>> + if (unlikely(ret))
>> + return ret;
>> +
>> return 0;
>> }
>> module_init(initialize_module);
>> --
>> 1.8.3.1
>>
next prev parent reply other threads:[~2018-03-08 1:57 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-01 9:09 [PATCH 1/4] module: Do not access sig_enforce directly Jia Zhang
2018-03-01 9:09 ` [PATCH 2/4] module: Create the entry point initialize_module() Jia Zhang
2018-03-01 9:09 ` [PATCH 3/4] module: Support to show the current enforcement policy Jia Zhang
2018-03-07 20:14 ` Jessica Yu
2018-03-08 1:57 ` Jia Zhang [this message]
2018-03-01 9:09 ` [PATCH 4/4] module: Allow to upgrade to validity enforcement in unforced mode Jia Zhang
2018-03-05 5:32 ` [PATCH 1/4] module: Do not access sig_enforce directly Jia Zhang
2018-03-08 4:26 [PATCH v2 0/4] modsign enhancement Jia Zhang
2018-03-08 4:27 ` [PATCH 3/4] module: Support to show the current enforcement policy Jia Zhang
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=a4393541-5240-3924-8d29-3449ddf616d8@linux.alibaba.com \
--to=zhang.jia@linux.alibaba.com \
--cc=jeyu@kernel.org \
--cc=linux-kernel@vger.kernel.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
all inboxes | Powered by JetHome®