From: Kylene Jo Hall <kjhall@us.ibm.com>
To: Stephen Smalley <sds@tycho.nsa.gov>
Cc: linux-kernel <linux-kernel@vger.kernel.org>,
LSM ML <linux-security-module@vger.kernel.org>,
Dave Safford <safford@us.ibm.com>, Mimi Zohar <zohar@us.ibm.com>,
Serge Hallyn <sergeh@us.ibm.com>,
akpm@osdl.org
Subject: Re: [PATCH 4/7] SLIM: secfs patch
Date: Mon, 18 Sep 2006 13:50:42 -0700 [thread overview]
Message-ID: <1158612642.16727.53.camel@localhost.localdomain> (raw)
In-Reply-To: <1158611418.14194.70.camel@moss-spartans.epoch.ncsc.mil>
On Mon, 2006-09-18 at 16:30 -0400, Stephen Smalley wrote:
> On Tue, 2006-09-12 at 10:57 -0700, Kylene Jo Hall wrote:
> > This patch provides the securityfs used by SLIM.
> >
> > Signed-off-by: Mimi Zohar <zohar@us.ibm.com>
> > Signed-off-by: Kylene Hall <kjhall@us.ibm.com>
> > ---
> > security/slim/slm_secfs.c | 73 ++++++++++++++++++++++++++++++++++++
> > 1 files changed, 73 insertions(+)
> >
> > --- linux-2.6.18/security/slim/slm_secfs.c 1969-12-31 16:00:00.000000000 -0800
> > +++ linux-2.6.17-working/security/slim/slm_secfs.c 2006-09-06 11:49:09.000000000 -0700
> > @@ -0,0 +1,73 @@
> > +/*
> > + * SLIM securityfs support: debugging control files
> > + *
> > + * Copyright (C) 2005, 2006 IBM Corporation
> > + * Author: Mimi Zohar <zohar@us.ibm.com>
> > + * Kylene Hall <kjhall@us.ibm.com>
> > + *
> > + * This program is free software; you can redistribute it and/or modify
> > + * it under the terms of the GNU General Public License as published by
> > + * the Free Software Foundation, version 2 of the License.
> > + */
> > +
> > +#include <asm/uaccess.h>
> > +#include <linux/config.h>
> > +#include <linux/module.h>
> > +#include <linux/kernel.h>
> > +#include <linux/security.h>
> > +#include <linux/debugfs.h>
> > +#include "slim.h"
> > +
> > +static struct dentry *slim_sec_dir, *slim_level;
> > +
> > +static ssize_t slm_read_level(struct file *file, char __user *buf,
> > + size_t buflen, loff_t *ppos)
> > +{
> > + struct slm_tsec_data *cur_tsec = current->security;
> > + ssize_t len;
> > + char data[28];
> > + if (is_kernel_thread(current))
> > + len = snprintf(data, sizeof(data), "KERNEL\n");
> > + else if (!cur_tsec)
> > + len = snprintf(data, sizeof(data), "UNKNOWN\n");
> > + else {
> > + if (cur_tsec->iac_wx != cur_tsec->iac_r)
> > + len = snprintf(data, sizeof(data), "GUARD wx:%s r:%s\n",
> > + slm_iac_str[cur_tsec->iac_wx],
> > + slm_iac_str[cur_tsec->iac_r]);
> > + else
> > + len = snprintf(data, sizeof(data), "%s\n",
> > + slm_iac_str[cur_tsec->iac_wx]);
> > + }
> > + return simple_read_from_buffer(buf, buflen, ppos, data, len);
> > +}
>
> Why do you need this when you implement getprocattr and return the same
> data that way?
>
True you can get the same info that way but we find it very useful to be
able to cat this file and get the level of the current process.
> > +
> > +static struct file_operations slm_level_ops = {
> > + .read = slm_read_level,
> > +};
> > +
> > +int __init slm_init_secfs(void)
> > +{
> > + if (!slim_enabled)
> > + return 0;
> > +
> > + slim_sec_dir = securityfs_create_dir("slim", NULL);
> > + if (!slim_sec_dir || IS_ERR(slim_sec_dir))
> > + return -EFAULT;
> > + slim_level = securityfs_create_file("level", S_IRUGO,
> > + slim_sec_dir, NULL, &slm_level_ops);
> > + if (!slim_level || IS_ERR(slim_level)) {
> > + securityfs_remove(slim_sec_dir);
> > + return -EFAULT;
> > + }
> > + return 0;
> > +}
> > +
> > +__initcall(slm_init_secfs);
> > +
> > +void __exit slm_cleanup_secfs(void)
> > +{
> > + securityfs_remove(slim_level);
> > + securityfs_remove(slim_sec_dir);
> > +}
> > +
>
Thanks,
Kylie
next prev parent reply other threads:[~2006-09-18 20:50 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-12 17:57 Kylene Jo Hall
2006-09-18 20:30 ` Stephen Smalley
2006-09-18 20:50 ` Kylene Jo Hall [this message]
2006-09-18 20:54 ` Dave Jones
2006-09-20 16:49 ` [PATCH] slim: cleanup use of config.h Kylene Jo Hall
2006-09-20 16:49 ` [PATCH] integrity: " Kylene Jo Hall
2006-09-27 12:30 ` [PATCH 4/7] SLIM: secfs patch Stephen Smalley
-- strict thread matches above, loose matches on Subject: below --
2006-08-23 19:05 Kylene Jo Hall
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=1158612642.16727.53.camel@localhost.localdomain \
--to=kjhall@us.ibm.com \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=safford@us.ibm.com \
--cc=sds@tycho.nsa.gov \
--cc=sergeh@us.ibm.com \
--cc=zohar@us.ibm.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome