Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.kernel > #1631588
| Path | csiph.com!aioe.org!bofh.it!news.nic.it!robomod |
|---|---|
| From | Casey Schaufler <casey@schaufler-ca.com> |
| Newsgroups | linux.kernel |
| Subject | Re: [PATCH 1/3] selinux: Implement LSM notification system |
| Date | Wed, 26 Apr 2017 18:20:02 +0200 |
| Message-ID | <tAxPA-4Ed-1@gated-at.bofh.it> (permalink) |
| References | <tAx3c-46S-13@gated-at.bofh.it> <tAxmx-4e9-3@gated-at.bofh.it> <tAxmx-4e9-1@gated-at.bofh.it> |
| X-Original-To | Daniel Jurgens <danielj@mellanox.com>, Sebastien Buisson <sbuisson.ddn@gmail.com>, "linux-security-module@vger.kernel.org" <linux-security-module@vger.kernel.org>, "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>, "selinux@tycho.nsa.gov" <selinux@tycho.nsa.gov> |
| Dkim-Signature | v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s2048; t=1493223091; bh=TVFi1+RYAGOqHGm51lS7Yk9axr9Vs88RA8ZNX1JWido=; h=Subject:To:References:Cc:From:Date:In-Reply-To:From:Subject; b=aausprs+u1ZPOVxqXijQtWmyAV8mkMNgPK4Ue/gcTUPxPHGXe6QJqe/hzJSiuzN26S2hMH/m0GgMTo+V3ntPLg9HozNzZIAAf8Kw5Qjgja3edP/BuZAYftavdnRZBmlw6gsbN0P6vg7BtHic+LZmTu3wYnpP+VxI62WvvxNCxJx68Cr4h+xW/x9jZuBq4c+MaQ07+TFrQi+kof206gbBvfkOwwfE5MyUm/7vZeMr3WN17WFc8HJOWgUQB7Hv7n3+wHXzwAM1UDDEU75IiCJoIBPc1viuhVt8m0GeHl0MJ8WvjsJt6QdS9j+ha9/8iM3VtmzAhSgeVeu5oP9ZOYg9HQ== |
| X-Yahoo-Newman-ID | 742419.62853.bm@smtp210.mail.ne1.yahoo.com |
| X-Yahoo-Newman-Property | ymail-3 |
| X-Ymail-Osg | 4p0X9yMVM1keedl7ZIeNWY_TRSelmb2AdVY0gB8joamo7bD 4VG7VpWqws4I199JrBBl4NdSqxZQ4vAauQU8ijWbkcB3hdnBt1njCrsPX5d3 C2EFRUqIYg_M7cF5bSRvvIza6o8T5.HCrDCLuP8TnU3sa_B0Eb5kd4Etx4eB DifYf1nVdhjmRcK.gv3B94kq1fJJHrJFV15d.jTwDalHm9PEpcZ1Irvfn57J Cea_Rny9BpZN1uMk_smjhqatIONMZVe3Dv8ub53C95R4d6IcsZIFUGZbaqyA KvwrIUzwSgvsHTSL1LvcdBcODavqU6y37B0OAOemdyk7uiQDlVOrHHEnp7yB NSoi9p.BR5nS19UzUBpl36nFFQylS4nxcAAyLlHKShtaeolinp3Oc.UKCDFJ SVIKYZGUQpzWPZ8ZnZSNBIvzNBfXoWbiNCoTbAgwX0PgUF88ccDlasx_4Hfa bTPtOuPsMKlNe2qsIuOckR1SZKb3dbxVPF9Es_A5ZZnZ5o5aiz7l7HT9SiWw ahYl05e6OohktertSq.dhJDhsA9xcAbgvHG.krgvi16YQYnV_PL_l7.qlAOa sCg-- |
| X-Yahoo-SMTP | OIJXglSswBDfgLtXluJ6wiAYv6_cnw-- |
| User-Agent | Mozilla/5.0 (Windows NT 10.0; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.8.0 |
| MIME-Version | 1.0 |
| Content-Type | text/plain; charset=windows-1252 |
| Content-Transfer-Encoding | 7bit |
| Sender | robomod@news.nic.it |
| List-ID | <linux-kernel.vger.kernel.org> |
| X-Mailing-List | linux-kernel@vger.kernel.org |
| Approved | robomod@news.nic.it |
| Lines | 147 |
| Organization | linux.* mail to news gateway |
| X-Original-Cc | "serge@hallyn.com" <serge@hallyn.com>, "james.l.morris@oracle.com" <james.l.morris@oracle.com>, "eparis@parisplace.org" <eparis@parisplace.org>, "sds@tycho.nsa.gov" <sds@tycho.nsa.gov>, "paul@paul-moore.com" <paul@paul-moore.com>, Sebastien Buisson <sbuisson@ddn.com> |
| X-Original-Date | Wed, 26 Apr 2017 09:11:26 -0700 |
| X-Original-Message-ID | <09a9df45-5c9b-aa7c-4b56-088278ac23f6@schaufler-ca.com> |
| X-Original-References | <1493218936-18522-1-git-send-email-sbuisson@ddn.com> <8d4c5ab6-8c15-312a-398b-c3ee9d7e8cb6@schaufler-ca.com> <DB5PR05MB09975186A082246C7649C94CC4110@DB5PR05MB0997.eurprd05.prod.outlook.com> |
| X-Original-Sender | linux-kernel-owner@vger.kernel.org |
| Xref | csiph.com linux.kernel:1631588 |
Show key headers only | View raw
On 4/26/2017 8:48 AM, Daniel Jurgens wrote:
> On 4/26/2017 10:38 AM, Casey Schaufler wrote:
>> On 4/26/2017 8:02 AM, Sebastien Buisson wrote:
>>> From: Daniel Jurgens <danielj@mellanox.com>
>>>
>>> Add a generic notification mechanism in the LSM. Interested consumers
>>> can register a callback with the LSM and security modules can produce
>>> events.
>> Why is this a generic mechanism? Do you ever see anyone
>> other than SELinux using it?
> I had created an SELinux specific mechanism, Paul Moore requested I make it generic.
>>> Add a call to the notification mechanism from SELinux when the AVC
>>> cache changes.
>> This seems like a whole lot of mechanism for
>> something you could accomplish with a log message.
>> What am I missing?
> This was part of a larger patch set that hasn't been accepted yet. SELinux support for Inifiniband. Subsequent patches in that patch set will use it as well.
You should include this information in a 0/3 message.
Without the context the patch set is curious, but not
compelling.
>>> Signed-off-by: Daniel Jurgens <danielj@mellanox.com>
>>> Signed-off-by: Sebastien Buisson <sbuisson@ddn.com>
>>> ---
>>> include/linux/security.h | 23 +++++++++++++++++++++++
>>> security/security.c | 20 ++++++++++++++++++++
>>> security/selinux/hooks.c | 12 ++++++++++++
>>> 3 files changed, 55 insertions(+)
>>>
>>> diff --git a/include/linux/security.h b/include/linux/security.h
>>> index af675b5..73a9c93 100644
>>> --- a/include/linux/security.h
>>> +++ b/include/linux/security.h
>>> @@ -68,6 +68,10 @@
>>> struct user_namespace;
>>> struct timezone;
>>>
>>> +enum lsm_event {
>>> + LSM_POLICY_CHANGE,
>>> +};
>>> +
>>> /* These functions are in security/commoncap.c */
>>> extern int cap_capable(const struct cred *cred, struct user_namespace *ns,
>>> int cap, int audit);
>>> @@ -163,6 +167,10 @@ struct security_mnt_opts {
>>> int num_mnt_opts;
>>> };
>>>
>>> +int call_lsm_notifier(enum lsm_event event, void *data);
>>> +int register_lsm_notifier(struct notifier_block *nb);
>>> +int unregister_lsm_notifier(struct notifier_block *nb);
>>> +
>>> static inline void security_init_mnt_opts(struct security_mnt_opts *opts)
>>> {
>>> opts->mnt_opts = NULL;
>>> @@ -381,6 +389,21 @@ int security_sem_semop(struct sem_array *sma, struct sembuf *sops,
>>> struct security_mnt_opts {
>>> };
>>>
>>> +static inline int call_lsm_notifier(enum lsm_event event, void *data)
>>> +{
>>> + return 0;
>>> +}
>>> +
>>> +static inline int register_lsm_notifier(struct notifier_block *nb)
>>> +{
>>> + return 0;
>>> +}
>>> +
>>> +static inline int unregister_lsm_notifier(struct notifier_block *nb)
>>> +{
>>> + return 0;
>>> +}
>>> +
>>> static inline void security_init_mnt_opts(struct security_mnt_opts *opts)
>>> {
>>> }
>>> diff --git a/security/security.c b/security/security.c
>>> index b9fea39..ef9d9e1 100644
>>> --- a/security/security.c
>>> +++ b/security/security.c
>>> @@ -32,6 +32,8 @@
>>> /* Maximum number of letters for an LSM name string */
>>> #define SECURITY_NAME_MAX 10
>>>
>>> +static ATOMIC_NOTIFIER_HEAD(lsm_notifier_chain);
>>> +
>>> struct security_hook_heads security_hook_heads __lsm_ro_after_init;
>>> char *lsm_names;
>>> /* Boot-time LSM user choice */
>>> @@ -146,6 +148,24 @@ void __init security_add_hooks(struct security_hook_list *hooks, int count,
>>> panic("%s - Cannot get early memory.\n", __func__);
>>> }
>>>
>>> +int call_lsm_notifier(enum lsm_event event, void *data)
>>> +{
>>> + return atomic_notifier_call_chain(&lsm_notifier_chain, event, data);
>>> +}
>>> +EXPORT_SYMBOL(call_lsm_notifier);
>>> +
>>> +int register_lsm_notifier(struct notifier_block *nb)
>>> +{
>>> + return atomic_notifier_chain_register(&lsm_notifier_chain, nb);
>>> +}
>>> +EXPORT_SYMBOL(register_lsm_notifier);
>>> +
>>> +int unregister_lsm_notifier(struct notifier_block *nb)
>>> +{
>>> + return atomic_notifier_chain_unregister(&lsm_notifier_chain, nb);
>>> +}
>>> +EXPORT_SYMBOL(unregister_lsm_notifier);
>>> +
>>> /*
>>> * Hook list operation macros.
>>> *
>>> diff --git a/security/selinux/hooks.c b/security/selinux/hooks.c
>>> index e67a526..a4d36f8 100644
>>> --- a/security/selinux/hooks.c
>>> +++ b/security/selinux/hooks.c
>>> @@ -171,6 +171,14 @@ static int selinux_netcache_avc_callback(u32 event)
>>> return 0;
>>> }
>>>
>>> +static int selinux_lsm_notifier_avc_callback(u32 event)
>>> +{
>>> + if (event == AVC_CALLBACK_RESET)
>>> + call_lsm_notifier(LSM_POLICY_CHANGE, NULL);
>>> +
>>> + return 0;
>>> +}
>>> +
>>> /*
>>> * initialise the security for the init task
>>> */
>>> @@ -6379,6 +6387,10 @@ static __init int selinux_init(void)
>>> if (avc_add_callback(selinux_netcache_avc_callback, AVC_CALLBACK_RESET))
>>> panic("SELinux: Unable to register AVC netcache callback\n");
>>>
>>> + if (avc_add_callback(selinux_lsm_notifier_avc_callback,
>>> + AVC_CALLBACK_RESET))
>>> + panic("SELinux: Unable to register AVC LSM notifier callback\n");
>>> +
>>> if (selinux_enforcing)
>>> printk(KERN_DEBUG "SELinux: Starting in enforcing mode\n");
>>> else
>
Back to linux.kernel | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
[PATCH 1/3] selinux: Implement LSM notification system Sebastien Buisson <sbuisson.ddn@gmail.com> - 2017-04-26 17:30 +0200
Re: [PATCH 1/3] selinux: Implement LSM notification system Daniel Jurgens <danielj@mellanox.com> - 2017-04-26 17:50 +0200
Re: [PATCH 1/3] selinux: Implement LSM notification system Sebastien Buisson <sbuisson.ddn@gmail.com> - 2017-04-26 18:00 +0200
Re: [PATCH 1/3] selinux: Implement LSM notification system Casey Schaufler <casey@schaufler-ca.com> - 2017-04-26 18:20 +0200
Re: [PATCH 1/3] selinux: Implement LSM notification system Casey Schaufler <casey@schaufler-ca.com> - 2017-04-26 17:50 +0200
Re: [PATCH 1/3] selinux: Implement LSM notification system Stephen Smalley <sds@tycho.nsa.gov> - 2017-04-26 19:40 +0200
Re: [PATCH 1/3] selinux: Implement LSM notification system Casey Schaufler <casey@schaufler-ca.com> - 2017-04-26 19:50 +0200
csiph-web