All of lore.kernel.org
 help / color / mirror / Atom feed
From: Darrel Goeddel <dgoeddel@TrustedCS.com>
To: Stephen Smalley <sds@tycho.nsa.gov>
Cc: SELinux List <selinux@tycho.nsa.gov>,
	Daniel Walsh <dwalsh@redhat.com>,
	Joshua Brindle <jbrindle@tresys.com>,
	Karl MacMillan <kmacmillan@mentalrootkit.com>,
	Linda Knippers <linda.knippers@hp.com>,
	Christopher PeBenito <cpebenito@tresys.com>
Subject: Re: [RFC PATCH 2/3] libselinux: define the "context" security class
Date: Thu, 05 Oct 2006 14:32:54 -0500	[thread overview]
Message-ID: <45255DE6.1090608@trustedcs.com> (raw)
In-Reply-To: <1160074008.2132.169.camel@moss-spartans.epoch.ncsc.mil>

Stephen Smalley wrote:
> On Thu, 2006-10-05 at 13:06 -0500, Darrel Goeddel wrote:
> 
>>Define a new security class "context" and its permission "translate" for
>>use by the context translation daemon.  The files are generated from the
>>current reference policy and have been altered by "make indent".  Note
>>the change in blank lines in av_permissions.h - should libselinux change,
>>should the script in the policy change, or should there be a manual
>>conversion?  The "polmatch" perm on the association class was also pulled
>>in from the policy.
> 
> 
> And setsockcreate removed, because refpolicy still doesn't have it.  Can
> someone add it, please?

D'oh,  I'll make sure that I don't remove that in a final patch.

> I think the divergence in blank lines is due to a change in the script
> (to avoid extraneous lines in the kernel headers), so we can just resync
> libselinux to the generated one.

Sounds good.  I think we should also modify the scripts in the policy to
generate the files in the style of "make indent".  Not terribly important
considering the easiness of make indent and the frequency of changes like
this.

I'll generate a kernel patch as well if this all flies.

-- 

Darrel

--
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:[~2006-10-05 19:32 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-10-05 18:06 [RFC PATCH 2/3] libselinux: define the "context" security class Darrel Goeddel
2006-10-05 18:46 ` Stephen Smalley
2006-10-05 19:32   ` Darrel Goeddel [this message]

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=45255DE6.1090608@trustedcs.com \
    --to=dgoeddel@trustedcs.com \
    --cc=cpebenito@tresys.com \
    --cc=dwalsh@redhat.com \
    --cc=jbrindle@tresys.com \
    --cc=kmacmillan@mentalrootkit.com \
    --cc=linda.knippers@hp.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.