All of lore.kernel.org
 help / color / mirror / Atom feed
From: Steve Lawrence <slawrence@tresys.com>
To: HarryCiao <harrytaurus2002@hotmail.com>
Cc: "Christopher J. PeBenito" <cpebenito@tresys.com>,
	<method@manicmethod.com>,
	selinux-mailing-list <selinux@tycho.nsa.gov>
Subject: Re: v3 Add role attribute support to libsepol
Date: Fri, 22 Jul 2011 15:51:37 -0400	[thread overview]
Message-ID: <4E29D4C9.3000903@tresys.com> (raw)
In-Reply-To: <SNT139-w20B1A1E8C4A8738E18E36AB580@phx.gbl>

--snip--

>>
>>>  > 2. The policy.X's binary representation and SELinux kernel role_datum_t
>>>  > structure don't have to be changed, so the max version number for 
>>> policy.X
>>>  > won't have to be bumped.
>>>  >
>>>  > But it may be desirable to bump the max module version number.
>>>  >
> 
> Write flavor flag and roles ebitmap into a pp file and read them out unconditionally, this would only run into problem only under one condition, that libsepol/checkpolicy are upgraded with this patchset but the pp files are built before the upgrade took place, which I think could be easily fixed by re-building all pp files by the upgraded libsepol/checkpolicy.
> 
> So I think we don't have to bump MOD_POLICYDB_VERSION_MAX higher.
> 
> Am I right?
> 
> BTW, how do we trigger a pp downgrade? Anything like OUTPUT_POLICY or policy-version to trigger policy downgrade?
> 
> Thanks,
> Harry
> 

There isn't a tool that can force a policy module downgrade, but it can
be done programmatically, so it should be supported. Additionally, it
shouldn't require that modules be rebuilt if the toolchain is updated.
So please add a new module version and check that before reading/writing
the new role attribute information.

Aside from that, I've reviewed this patchset and everything looks
reasonable. I still want to test this a little more, but assuming I
don't see any any issues with a little more testing, and pending a fix
for a module version bump, I'm fine with merging this.

- Steve

--
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-07-22 19:51 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-06-28  8:18 v3 Add role attribute support to libsepol Harry Ciao
2011-06-28  8:18 ` [v3 PATCH 1/6] Add role attribute support when compiling modules Harry Ciao
2011-06-28  8:18 ` [v3 PATCH 2/6] Add role attribute support when generating pp files Harry Ciao
2011-06-28  8:18 ` [v3 PATCH 3/6] Add role attribute support when linking modules Harry Ciao
2011-06-28  8:18 ` [v3 PATCH 4/6] Add role attribute support when expanding role_datum_t Harry Ciao
2011-06-28  8:18 ` [v3 PATCH 5/6] Add role attribute support when expanding role_set_t Harry Ciao
2011-06-28  8:18 ` [v3 PATCH 6/6] Support adding one role attribute into another Harry Ciao
2011-06-28  8:28 ` v3 Add role attribute support to libsepol HarryCiao
2011-06-29  7:14   ` Harry Ciao
2011-06-30  7:11     ` HarryCiao
2011-07-22 19:51       ` Steve Lawrence [this message]
2011-07-23 10:05         ` 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=4E29D4C9.3000903@tresys.com \
    --to=slawrence@tresys.com \
    --cc=cpebenito@tresys.com \
    --cc=harrytaurus2002@hotmail.com \
    --cc=method@manicmethod.com \
    --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.