All of lore.kernel.org
 help / color / mirror / Atom feed
From: Darrel Goeddel <dgoeddel@TrustedCS.com>
To: Joshua Brindle <jbrindle@tresys.com>
Cc: SELinux List <selinux@tycho.nsa.gov>,
	Stephen Smalley <sds@tycho.nsa.gov>,
	Karl MacMillan <kmacmillan@mentalrootkit.com>,
	Linda Knippers <linda.knippers@hp.com>,
	Daniel Walsh <dwalsh@redhat.com>
Subject: Re: [PATCH 1/4] libselinux flask definition update for context class
Date: Tue, 17 Oct 2006 13:02:38 -0500	[thread overview]
Message-ID: <45351ABE.3050006@trustedcs.com> (raw)
In-Reply-To: <453518AB.4020303@tresys.com>

Joshua Brindle wrote:
> Darrel Goeddel wrote:
> 
>> Update SELinux flask definition to include the context security class.
>> This also adds the "process setsockcreate" and "association polmatch" 
>> string
>> definitions that have been missing.
>>
>> Signed-off-by: Darrel Goeddel <dgoeddel@trustedcs.com>
>>
>> ---
>>
>> include/selinux/av_permissions.h |   76 
>> ---------------------------------------
> 
> 
> Why all the whitespace changes?

Those are the files created by using the tolib target in the flask directory
of the references policy (with Lindent changes...).  The same is true for the
kernel patch (except for the Lindent).  I asked about that earlier and was
guided to go with the generated files.

-- 

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-17 18:02 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-10-17 15:59 [PATCH 1/4] libselinux flask definition update for context class Darrel Goeddel
2006-10-17 17:53 ` Joshua Brindle
2006-10-17 18:02   ` Darrel Goeddel [this message]
2006-10-17 18:19     ` Eric Paris
2006-10-19 13:52 ` Stephen Smalley

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=45351ABE.3050006@trustedcs.com \
    --to=dgoeddel@trustedcs.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.