All of lore.kernel.org
 help / color / mirror / Atom feed
From: Joshua Brindle <method@manicmethod.com>
To: Harry Ciao <qingtao.cao@windriver.com>
Cc: cpebenito@tresys.com, sds@tycho.nsa.gov, jmorris@namei.org,
	eparis@parisplace.org, selinux@tycho.nsa.gov
Subject: Re: [v1 PATCH 1/6] Add role attribute support when compiling modules.
Date: Sun, 29 May 2011 18:57:38 -0400	[thread overview]
Message-ID: <4DE2CF62.4060909@manicmethod.com> (raw)
In-Reply-To: <1306643819-30374-2-git-send-email-qingtao.cao@windriver.com>

Harry Ciao wrote:
> 1. Add a uint32_t "flavor" field and an ebitmap "roles" to the
> role_datum_t structure;
>
> 2. Modify the attribute declaration rule to add support to declare
> role attribute as well as type attribute;

Lets just use a different token to declare role attributes and use 
separate parser functions. I strongly dislike the char *kind in 
define_attrib(). Overloading tokens has caused much pain in the past.

>
> 3. Modify declare_role() to setup role_datum_t.flavor according
> to the isattr argument;
>
> 4. Add a new roleattribute rule and its handler, which will record
> the regular role's (policy value - 1) into the role attribute's
> role_datum_t.roles ebitmap;
>
> 5. Modify the syntax for the role_types rule only to define the
> role-type associations;
>
> 6. Add a new role_attr rule to support the declaration of a single
> role, and the role attribute that the role belongs to;
>
> 7. Check if the new_role used in role transition is a regular role;
>
> 8. Make the role-types rule no longer used to declare a regular role
> but solely aimed for declaring role-types associations;
>
> FIXME:
> How to pass a second argument to require_attribute(), to indicate
> if the attribute is of role or type ?

My suggestion on #2 should resolve this.

I'll look at the other patches soon.

--
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.

  reply	other threads:[~2011-05-29 22:57 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-29  4:36 v1 Add role attribute support to libsepol Harry Ciao
2011-05-29  4:36 ` [v1 PATCH 1/6] Add role attribute support when compiling modules Harry Ciao
2011-05-29 22:57   ` Joshua Brindle [this message]
2011-05-30  6:59     ` HarryCiao
2011-05-29  4:36 ` [v1 PATCH 2/6] Add role attribute support when generating pp files Harry Ciao
2011-05-29  4:36 ` [v1 PATCH 3/6] Add role attribute support when linking modules Harry Ciao
2011-05-29  4:36 ` [v1 PATCH 4/6] Add role attribute support when expanding role_datum_t Harry Ciao
2011-05-29  4:36 ` [v1 PATCH 5/6] Add role attribute support when expanding role_set_t Harry Ciao
2011-05-29  4:51 ` v1 Add role attribute support to libsepol HarryCiao
2011-05-29 10:41   ` HarryCiao

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=4DE2CF62.4060909@manicmethod.com \
    --to=method@manicmethod.com \
    --cc=cpebenito@tresys.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.