From: Joshua Brindle <method@manicmethod.com>
To: Harry Ciao <qingtao.cao@windriver.com>
Cc: sds@tycho.nsa.gov, jmorris@namei.org, eparis@parisplace.org,
selinux@tycho.nsa.gov
Subject: Re: [v0 PATCH 3/5] Handle the class in role_trans structure
Date: Wed, 23 Mar 2011 09:26:17 -0400 [thread overview]
Message-ID: <4D89F4F9.6010200@manicmethod.com> (raw)
In-Reply-To: <1300847325-20308-7-git-send-email-qingtao.cao@windriver.com>
Harry Ciao wrote:
> From: Harry Ciao<harrytaurus2002@hotmail.com>
>
> Add the class support to various functions that handle the role_trans
> structure.
>
> Signed-off-by: Harry Ciao<qingtao.cao@windriver.com>
> ---
> libsepol/src/policydb.c | 28 ++++++++++++++++++++++++----
> libsepol/src/write.c | 22 +++++++++++++++++-----
> 2 files changed, 41 insertions(+), 9 deletions(-)
>
> diff --git a/libsepol/src/policydb.c b/libsepol/src/policydb.c
> index 5c0081f..9b43c56 100644
> --- a/libsepol/src/policydb.c
> +++ b/libsepol/src/policydb.c
> @@ -137,6 +137,13 @@ static struct policydb_compat_info policydb_compat[] = {
> .target_platform = SEPOL_TARGET_SELINUX,
> },
> {
> + .type = POLICY_KERN,
> + .version = POLICYDB_VERSION_ROLETRANS,
> + .sym_num = SYM_NUM,
> + .ocon_num = OCON_NODE6 + 1,
> + .target_platform = SEPOL_TARGET_SELINUX,
> + },
> + {
> .type = POLICY_BASE,
> .version = MOD_POLICYDB_VERSION_BASE,
> .sym_num = SYM_NUM,
Why just the kernel version? There should be a module version that supports this
also. Have you attempted to write out modules with classes in role_trans rules?
--
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:[~2011-03-23 13:26 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-23 2:28 v0 Add class support to the role_transition rule Harry Ciao
2011-03-23 2:28 ` [v0 PATCH 1/3] SELinux: Add class support to the role_trans structure Harry Ciao
2011-03-23 14:40 ` Eric Paris
2011-03-24 9:43 ` HarryCiao
2011-03-24 13:21 ` Stephen Smalley
2011-03-25 6:28 ` HarryCiao
2011-03-23 2:28 ` [v0 PATCH 2/3] SELinux: Compute role in newcontext for all classes Harry Ciao
2011-03-23 13:31 ` Stephen Smalley
2011-03-24 9:56 ` HarryCiao
2011-03-24 13:25 ` Stephen Smalley
2011-03-25 6:25 ` HarryCiao
2011-03-23 14:46 ` Eric Paris
2011-03-23 2:28 ` [v0 PATCH 3/3] SELinux: Write class field in role_trans_write Harry Ciao
2011-03-23 14:48 ` Eric Paris
2011-03-23 18:59 ` Joshua Brindle
2011-03-24 10:02 ` HarryCiao
2011-03-23 2:28 ` [v0 PATCH 1/5] Add class to role_trans & role_trans_rule Harry Ciao
2011-03-23 2:28 ` [v0 PATCH 2/5] Make role_transition parser to handle class field Harry Ciao
2011-03-23 19:30 ` Eric Paris
2011-03-23 19:41 ` Joshua Brindle
2011-03-23 20:14 ` Eric Paris
2011-03-23 2:28 ` [v0 PATCH 3/5] Handle the class in role_trans structure Harry Ciao
2011-03-23 13:26 ` Joshua Brindle [this message]
2011-03-23 19:05 ` Joshua Brindle
2011-03-24 10:36 ` HarryCiao
2011-03-23 2:28 ` [v0 PATCH 4/5] Handle the class in role_trans_rule structure Harry Ciao
2011-03-23 2:28 ` [v0 PATCH 5/5] Display the class in role_transition rule Harry Ciao
2011-03-23 8:21 ` v0 Add class support to the " Harry Ciao
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=4D89F4F9.6010200@manicmethod.com \
--to=method@manicmethod.com \
--cc=eparis@parisplace.org \
--cc=jmorris@namei.org \
--cc=qingtao.cao@windriver.com \
--cc=sds@tycho.nsa.gov \
--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.