From: Casey Schaufler <casey@schaufler-ca.com>
To: "Ahmed S. Darwish" <darwish.07@gmail.com>,
Stephen Smalley <sds@tycho.nsa.gov>
Cc: casey@schaufler-ca.com, Andrew Morton <akpm@linux-foundation.org>,
James Morris <jmorris@namei.org>, Paul Moore <paul.moore@hp.com>,
LKML <linux-kernel@vger.kernel.org>,
LSM-ML <linux-security-module@vger.kernel.org>,
Audit-ML <linux-audit@redhat.com>,
Steve Grubb <sgrubb@redhat.com>
Subject: Re: [RFC][PATCH -v2] Smack: Integrate with Audit
Date: Wed, 12 Mar 2008 11:09:39 -0700 (PDT) [thread overview]
Message-ID: <423839.91626.qm@web36615.mail.mud.yahoo.com> (raw)
In-Reply-To: <20080312164358.GA9540@ubuntu>
--- "Ahmed S. Darwish" <darwish.07@gmail.com> wrote:
>
> > Perhaps I misunderstand, but Smack labels don't represent users (i.e.
> > user identity) in any way, so it seemed like a mismatch to use the _USER
> > flag there. Whereas types in SELinux bear some similarity to Smack
> > labels - simple unstructured names whose meaning is only defined by the
> > policy rules.
> >
>
> I think Casey meant the common use of Smack where a login program
> (openssh, bin/login, ..) sets a label for each user that logs in, thus
> letting each label effectively representing a user.
No, I really just don't care which name gets used because none
of them map properly but I don't see value in adding a new one.
I say _USER is fine. I dislike _TYPE because it implies structure
that isn't there and I dislike _ROLE because someone may want to
implement roles on top of Smack (it wouldn't be hard) and don't
want to start using that term for a specific meaning that might
give 'em fits.
>
> In a sense, smack labels share a bit of _USER and _TYPE.
And maybe _ROLE, if you look at it from the right angle.
I don't think that it matters. Create a new _LATEFORDINNER
if that makes y'all feel better. Best of all would be to
stick with _USER and call it done.
Thank you.
Casey Schaufler
casey@schaufler-ca.com
next prev parent reply other threads:[~2008-03-12 18:09 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-10 12:49 [RFC][PATCH] Smack<->Audit integration Ahmed S. Darwish
2008-03-10 16:07 ` Casey Schaufler
2008-03-10 18:26 ` Ahmed S. Darwish
2008-03-10 18:43 ` Casey Schaufler
2008-03-12 2:44 ` [RFC][PATCH -v2] Smack: Integrate with Audit Ahmed S. Darwish
2008-03-12 4:23 ` Casey Schaufler
2008-03-12 12:18 ` [PATCH -v2b] " Ahmed S. Darwish
2008-03-12 12:52 ` [RFC][PATCH -v2] " Stephen Smalley
2008-03-12 15:40 ` Casey Schaufler
2008-03-12 15:48 ` Stephen Smalley
2008-03-12 16:23 ` Linda Knippers
2008-03-12 16:43 ` Ahmed S. Darwish
2008-03-12 18:09 ` Casey Schaufler [this message]
2008-03-13 13:55 ` Steve Grubb
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=423839.91626.qm@web36615.mail.mud.yahoo.com \
--to=casey@schaufler-ca.com \
--cc=akpm@linux-foundation.org \
--cc=darwish.07@gmail.com \
--cc=jmorris@namei.org \
--cc=linux-audit@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=paul.moore@hp.com \
--cc=sds@tycho.nsa.gov \
--cc=sgrubb@redhat.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