All of lore.kernel.org
 help / color / mirror / Atom feed
From: flihp@twobit.us (Philip Tricca)
To: refpolicy@oss.tresys.com
Subject: [refpolicy] RFC: macro expansion in monolithic policy: seusers
Date: Thu, 11 Aug 2011 15:07:13 -0400	[thread overview]
Message-ID: <4E442861.5000801@twobit.us> (raw)

While playing with a monolithic policy this morning I noticed that calls 
to getseuserbyname were returning a strange level string 
("s0-mcs_systemhigh") and breaking subsequent calls to 
get_default_context_with_level.  The culprit turned out to be unexpanded 
macros in /etc/selinux/$(NAME)/seusers.

For a modular policy the source file ./config/appconfig-$(TYPE)/seusers 
gets run through m4, output to ./tmp, then included in the base module. 
   For a monolithic policy, the Rules.monolithic file just copies 
seusers from ./config/appconfig-$(TYPE) to the destination without 
passing it through the m4 processor.

I was working with the 20100524 release and, if this is a bug and not my 
misunderstanding, it's present up to the current head of the development 
tree.  In the attached patch I've moved the m4 processing step from the 
Rules.modular file to the main Makefile and fixed up the install target 
for seusers in Rules.monolithic.

Has it really been this long since someone's built a monolithic policy 
or am I missing something?

Comments from the list would be appreciated,
- Philip

-------------- next part --------------
A non-text attachment was scrubbed...
Name: seusers-build.diff
Type: text/x-diff
Size: 1881 bytes
Desc: not available
Url : http://oss.tresys.com/pipermail/refpolicy/attachments/20110811/85e90892/attachment.bin 

             reply	other threads:[~2011-08-11 19:07 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-08-11 19:07 Philip Tricca [this message]
2011-08-12 12:31 ` [refpolicy] RFC: macro expansion in monolithic policy: seusers Christopher J. PeBenito

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=4E442861.5000801@twobit.us \
    --to=flihp@twobit.us \
    --cc=refpolicy@oss.tresys.com \
    /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.