From: Ivan Gyurdiev <ivg2@cornell.edu>
To: Chad Hanson <chanson@TrustedCS.com>
Cc: "'SELinux List '" <SELinux@tycho.nsa.gov>,
"'Stephen Smalley '" <sds@tycho.nsa.gov>,
"'Joshua Brindle '" <jbrindle@tresys.com>
Subject: Re: [SEPOL][SEMANAGE] Nodecon Support: Try 1
Date: Fri, 10 Feb 2006 22:34:20 -0500 [thread overview]
Message-ID: <43ED5B3C.9090406@cornell.edu> (raw)
In-Reply-To: <36282A1733C57546BE392885C061859205735A@chaos.tcs.tcs-sec.com>
> I guess I need to correct myself, that checkpolicy, not the kernel orders
> the nodecon rules.
>
> http://marc.theaimsgroup.com/?l=selinux&m=109906728301734&w=2
> http://marc.theaimsgroup.com/?l=selinux&m=109968743026327&w=2
> http://cvs.sourceforge.net/viewcvs.py/selinux/nsa/selinux-usr/checkpolicy/po
> licy_parse.y?r1=1.24&r2=1.25
>
Ah, this makes all the difference... then the original plan makes sense,
and the patch should work, once ordering is added in the local case. I
should be able to make a nodecon spec take precedence by placing it in
front of the ocontext_t list, correct?
The ports issue I described stands anyway, list() and iterate() show
overlapping ranges, and that will be an issue for nodes as well.
--
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-02-11 3:34 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-11 1:55 [SEPOL][SEMANAGE] Nodecon Support: Try 1 Chad Hanson
2006-02-11 3:34 ` Ivan Gyurdiev [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-02-05 21:01 Ivan Gyurdiev
2006-02-06 1:07 ` Ivan Gyurdiev
2006-02-08 8:21 ` Ivan Gyurdiev
2006-02-10 23:21 ` Ivan Gyurdiev
2006-02-14 19:02 ` Stephen Smalley
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=43ED5B3C.9090406@cornell.edu \
--to=ivg2@cornell.edu \
--cc=SELinux@tycho.nsa.gov \
--cc=chanson@TrustedCS.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.