LKML Archive on lore.kernel.org help / color / mirror / Atom feed
From: "Ahmed S. Darwish" <darwish.07@gmail.com> To: Chris Wright <chrisw@sous-sol.org>, Stephen Smalley <sds@tycho.nsa.gov>, James Morris <jmorris@namei.org>, Eric Paris <eparis@parisplace.org>, Casey Schaufler <casey@schaufler-ca.com>, David Woodhouse <dwmw2@infradead.org> Cc: linux-security-module@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>, akpm <akpm@linux-foundation.org> Subject: [PATCH -mm 0/4] LSM interfaced Audit (SELinux audit separation) Date: Wed, 27 Feb 2008 01:22:29 +0200 [thread overview] Message-ID: <20080226232229.GA12059@ubuntu> (raw) Hi everybody, This is a beginning of work (started and suggested by Casey Schaufler) to let Audit be LSM neutral. This is done for proper audit<->SMACK integration which will also be useful for any future LSM. What follows is four patches to remove the following exported SElinux interfaces: selinux_get_inode_sid(inode, sid) selinux_get_ipc_sid(ipcp, sid) selinux_get_task_sid(tsk, sid) selinux_sid_to_string(sid, ctx, len) and substitue them respectively with: new LSM hook, inode_getsecid(inode, secid) new LSM hook, ipc_getsecid*(ipcp, secid) LSM hook, task_getsecid(tsk, secid) LSM hook, sid_to_secctx(sid, ctx, len) The work isn't complete yet, and those four patches are sent for an early review. A new LSM interfaces/hooks will be created to substitute the SELinux exported audit interfaces, thus completing the separation. It's worthy to note that those changes can be merged in their current state. The tree is fully grepped to make sure that no subsystem ,except the patched ones, will be affected by this SELinux API breakage. Diffstat: include/linux/security.h | 23 +++++++++++++++- include/linux/selinux.h | 62 --------------------------------------------- kernel/audit.c | 14 +++++----- kernel/auditfilter.c | 5 ++- kernel/auditsc.c | 37 +++++++++++++------------- net/netlink/af_netlink.c | 3 -- security/dummy.c | 16 ++++++++++- security/security.c | 12 ++++++++ security/selinux/exports.c | 42 ------------------------------ security/selinux/hooks.c | 19 ++++++++++++- 10 files changed, 95 insertions(+), 138 deletions(-) Thanks in advance for your reviews and comments. -- Ahmed S. Darwish Blog: http://darwish-07.blogspot.com Homepage: http://darwish.07.googlepages.com
next reply other threads:[~2008-02-26 23:25 UTC|newest] Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top 2008-02-26 23:22 Ahmed S. Darwish [this message] 2008-02-26 23:24 ` [PATCH -mm 1/4] LSM: Introduce inode_getsecid and ipc_getsecid hooks Ahmed S. Darwish 2008-02-27 16:04 ` Paul Moore 2008-02-27 16:45 ` Ahmed S. Darwish 2008-02-26 23:25 ` [PATCH -mm 2/4] SELinux: Remove various exported symbols Ahmed S. Darwish 2008-02-26 23:42 ` Paul Moore 2008-02-26 23:28 ` [PATCH -mm 3/4] Audit: start not to use SELinux " Ahmed S. Darwish 2008-02-27 16:00 ` Paul Moore 2008-02-27 17:11 ` Ahmed S. Darwish 2008-02-27 22:25 ` James Morris 2008-02-26 23:31 ` [PATCH -mm 4/4] Netlink: Use LSM interface instead of SELinux one Ahmed S. Darwish
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=20080226232229.GA12059@ubuntu \ --to=darwish.07@gmail.com \ --cc=akpm@linux-foundation.org \ --cc=casey@schaufler-ca.com \ --cc=chrisw@sous-sol.org \ --cc=dwmw2@infradead.org \ --cc=eparis@parisplace.org \ --cc=jmorris@namei.org \ --cc=linux-kernel@vger.kernel.org \ --cc=linux-security-module@vger.kernel.org \ --cc=sds@tycho.nsa.gov \ /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: linkBe 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).