From: Casey Schaufler <casey@schaufler-ca.com>
To: James Morris <jmorris@namei.org>,
Casey Schaufler <casey@schaufler-ca.com>
Cc: SELinux List <selinux@tycho.nsa.gov>
Subject: Re: Scope of SECMARK_MODE_SEL
Date: Sat, 4 Aug 2007 11:20:18 -0700 (PDT) [thread overview]
Message-ID: <914026.68329.qm@web36613.mail.mud.yahoo.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0708031433510.25207@us.intercode.com.au>
--- James Morris <jmorris@namei.org> wrote:
> On Fri, 3 Aug 2007, Casey Schaufler wrote:
>
> >
> > It is my assumption that SECMARK_MODE_SEL is defined and coded solely
> > for use by SELinux and that it is not intended as a general purpose
> > secmark for any random LSM to use. I assume that if another LSM wants
> > to use SECMARK that it needs to supply its own SECMARK_MODE value and
> > checkentry function.
> >
> > Are my assumptions accurate?
>
> Yes, and you likely also need to add your own entry to the union in
> struct xt_secmark_target_info, which I'd guess would simply be a smack_t.
Thank you. My question was really aimed at finding out if the
code should be changed as part of the effort to pull SELinux
dependencies out of the audit code. Smack and xfrm is a distinct
set of work.
Casey Schaufler
casey@schaufler-ca.com
--
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.
prev parent reply other threads:[~2007-08-04 18:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-03 19:53 Scope of SECMARK_MODE_SEL Casey Schaufler
2007-08-03 21:38 ` James Morris
2007-08-04 18:20 ` Casey Schaufler [this message]
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=914026.68329.qm@web36613.mail.mud.yahoo.com \
--to=casey@schaufler-ca.com \
--cc=jmorris@namei.org \
--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.