From: "Serge E. Hallyn" <serue@us.ibm.com>
To: Casey Schaufler <casey@schaufler-ca.com>
Cc: Oren Laadan <orenl@cs.columbia.edu>,
Linux Containers <containers@lists.osdl.org>,
linux-security-module@vger.kernel.org,
SELinux <selinux@tycho.nsa.gov>
Subject: Re: [RFC PATCH 2/2] cr: debug security_checkpoint_header and security_may_restart
Date: Fri, 4 Sep 2009 08:46:11 -0500 [thread overview]
Message-ID: <20090904134611.GA11508@us.ibm.com> (raw)
In-Reply-To: <4AA0A3AE.9040106@schaufler-ca.com>
Quoting Casey Schaufler (casey@schaufler-ca.com):
> Serge E. Hallyn wrote:
> > This patch, for debugging only, introduces a silly admin-controlled
> > 'policy version' for smack. By default the version is 1. An
> > admin (with CAP_MAC_ADMIN) can change it by echoing a new value
> > into /smack/version.
> >
>
> The scheme you have suggested is just one step off of completely
> acceptable for real. More detail below, but if you make the "version"
> a string instead of a number I'm happy with it. In particular, a
> string that would itself be a valid Smack label makes everything
> really simple.
Presumably at many sites the version will be a unique string not
used as a label anywhere else. That's ok?
> It would take me a few days, but if you're not in a real hurry or
> you're lazier than I am (yeah, right) I could provide a patch that
> does it. Or, if I haven't been completely incomprehensible, you
> could do a revision.
Heh, I'm in no hurry. I'll mark this to do midway next week, if
you haven't gotten around to it first. Thanks!
-serge
WARNING: multiple messages have this Message-ID (diff)
From: "Serge E. Hallyn" <serue@us.ibm.com>
To: Casey Schaufler <casey@schaufler-ca.com>
Cc: Oren Laadan <orenl@cs.columbia.edu>,
Linux Containers <containers@lists.osdl.org>,
linux-security-module@vger.kernel.org,
SELinux <selinux@tycho.nsa.gov>
Subject: Re: [RFC PATCH 2/2] cr: debug security_checkpoint_header and security_may_restart
Date: Fri, 4 Sep 2009 08:46:11 -0500 [thread overview]
Message-ID: <20090904134611.GA11508@us.ibm.com> (raw)
In-Reply-To: <4AA0A3AE.9040106@schaufler-ca.com>
Quoting Casey Schaufler (casey@schaufler-ca.com):
> Serge E. Hallyn wrote:
> > This patch, for debugging only, introduces a silly admin-controlled
> > 'policy version' for smack. By default the version is 1. An
> > admin (with CAP_MAC_ADMIN) can change it by echoing a new value
> > into /smack/version.
> >
>
> The scheme you have suggested is just one step off of completely
> acceptable for real. More detail below, but if you make the "version"
> a string instead of a number I'm happy with it. In particular, a
> string that would itself be a valid Smack label makes everything
> really simple.
Presumably at many sites the version will be a unique string not
used as a label anywhere else. That's ok?
> It would take me a few days, but if you're not in a real hurry or
> you're lazier than I am (yeah, right) I could provide a patch that
> does it. Or, if I haven't been completely incomprehensible, you
> could do a revision.
Heh, I'm in no hurry. I'll mark this to do midway next week, if
you haven't gotten around to it first. Thanks!
-serge
--
This message was distributed to subscribers of the selinux mailing list.
If you no longer wish to subscribe, send mail to majordomo@tycho.nsa.gov with
the words "unsubscribe selinux" without quotes as the message.
next prev parent reply other threads:[~2009-09-04 13:46 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-03 22:28 [RFC PATCH 1/2] cr: lsm: provide hooks for an LSM to track policy changes Serge E. Hallyn
2009-09-03 22:28 ` Serge E. Hallyn
2009-09-03 22:28 ` [RFC PATCH 2/2] cr: debug security_checkpoint_header and security_may_restart Serge E. Hallyn
2009-09-03 22:28 ` Serge E. Hallyn
2009-09-04 5:20 ` Casey Schaufler
2009-09-04 5:20 ` Casey Schaufler
2009-09-04 13:46 ` Serge E. Hallyn [this message]
2009-09-04 13:46 ` Serge E. Hallyn
2009-09-07 18:31 ` Casey Schaufler
2009-09-07 18:31 ` Casey Schaufler
2009-09-08 4:12 ` Serge E. Hallyn
2009-09-08 4:12 ` Serge E. Hallyn
2009-09-09 4:43 ` Casey Schaufler
2009-09-09 4:43 ` Casey Schaufler
2009-09-09 14:35 ` Serge E. Hallyn
2009-09-09 14:35 ` Serge E. Hallyn
2009-09-09 14:52 ` Casey Schaufler
2009-09-09 14:52 ` Casey Schaufler
2009-09-09 19:46 ` Serge E. Hallyn
2009-09-09 19:46 ` Serge E. Hallyn
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=20090904134611.GA11508@us.ibm.com \
--to=serue@us.ibm.com \
--cc=casey@schaufler-ca.com \
--cc=containers@lists.osdl.org \
--cc=linux-security-module@vger.kernel.org \
--cc=orenl@cs.columbia.edu \
--cc=selinux@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: 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.