From: Karl MacMillan <kmacmillan@mentalrootkit.com>
To: Joshua Brindle <jbrindle@tresys.com>
Cc: Darrel Goeddel <dgoeddel@TrustedCS.com>,
SELinux List <SELinux@tycho.nsa.gov>,
Stephen Smalley <sds@tycho.nsa.gov>,
Eric Paris <eparis@redhat.com>
Subject: RE: [PATCH 2/2 take 2] userland support for new range_transition statements
Date: Wed, 09 Aug 2006 09:09:16 -0400 [thread overview]
Message-ID: <1155128956.942.2.camel@localhost.localdomain> (raw)
In-Reply-To: <6FE441CD9F0C0C479F2D88F959B0158832AE65@exchange.columbia.tresys.com>
On Tue, 2006-08-08 at 18:25 -0400, Joshua Brindle wrote:
> > From: Darrel Goeddel [mailto:dgoeddel@trustedcs.com]
> >
>
> Sorry it took so long to reply to this.
>
> >
> > for module policy versions up to 6, there are no
> > range_transitions for base policy versions 6 and up, an
>
> This is only per the grammar right? You are writing range_trans_rule_t's
> in every avrule block so version 6 does support them, just not the
> grammar yet.
>
>
> > #if 0
> > @@ -307,6 +326,32 @@
> > }
> > }
> >
> > +void range_trans_rule_init(range_trans_rule_t *x) {
> > + type_set_init(&x->stypes);
> > + type_set_init(&x->ttypes);
> > + ebitmap_init(&x->tclasses);
> > + mls_range_init(&x->trange);
> > +}
>
> x->next = NULL?
>
>
> That's all I have, looks good sans the semantic range representation.
>
I vote we punt on this - it is only needed for modules and this work
won't get us module support without another format change anyway (to
support mls requirements). If this is going to make fc6 it needs to be
done soon and I would rather be close and in fc6 than perfect and not.
Karl
>
> --
> 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.
--
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:[~2006-08-09 13:09 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-28 15:13 [PATCH 2/2] userland support for new range_transition statements Darrel Goeddel
2006-07-31 16:40 ` Stephen Smalley
2006-07-31 18:25 ` Darrel Goeddel
2006-07-31 18:29 ` Karl MacMillan
2006-07-31 18:54 ` Darrel Goeddel
2006-07-31 20:52 ` Stephen Smalley
2006-08-01 13:14 ` Joshua Brindle
2006-08-02 16:38 ` Darrel Goeddel
2006-08-02 19:51 ` Karl MacMillan
2006-08-02 21:59 ` Darrel Goeddel
2006-08-03 12:01 ` Joshua Brindle
2006-08-03 15:55 ` Joshua Brindle
2006-08-04 16:13 ` Darrel Goeddel
2006-08-07 13:18 ` Joshua Brindle
2006-08-08 14:48 ` Darrel Goeddel
2006-08-08 22:45 ` Joshua Brindle
2006-08-09 15:00 ` Darrel Goeddel
2006-08-04 17:10 ` [PATCH 2/2 take 2] " Darrel Goeddel
2006-08-08 22:25 ` Joshua Brindle
2006-08-09 13:09 ` Karl MacMillan [this message]
2006-08-09 13:31 ` Joshua Brindle
2006-08-09 15:06 ` Darrel Goeddel
2006-08-09 15:13 ` Karl MacMillan
2006-08-09 15:39 ` [PATCH 2/2 take 2] userland support for new range_transitionstatements Joshua Brindle
2006-08-09 14:29 ` [PATCH 2/2 take 2] userland support for new range_transition statements Darrel Goeddel
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=1155128956.942.2.camel@localhost.localdomain \
--to=kmacmillan@mentalrootkit.com \
--cc=SELinux@tycho.nsa.gov \
--cc=dgoeddel@TrustedCS.com \
--cc=eparis@redhat.com \
--cc=jbrindle@tresys.com \
--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: 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.