All of lore.kernel.org
 help / color / mirror / Atom feed
From: Daniel J Walsh <dwalsh@redhat.com>
To: "Christopher J. PeBenito" <cpebenito@tresys.com>
Cc: Karl MacMillan <kmacmillan@mentalrootkit.com>,
	Steve G <linux_4ever@yahoo.com>, SE Linux <selinux@tycho.nsa.gov>
Subject: Re: Patch to cleanup audit handling in policy.
Date: Thu, 03 May 2007 09:11:58 -0400	[thread overview]
Message-ID: <4639DF9E.70405@redhat.com> (raw)
In-Reply-To: <1178194665.445.42.camel@sgc.columbia.tresys.com>

I agree with Karl here.  I think while these are different types of 
interfaces, they are definitely related to doing auditing.  As a policy 
writer I would look into the logging.if for these interfaces and not 
seeing them would write them by hand, probably badly.  (As we have seen 
by the number of times it was done wrong.)  I would not think to look in 
a random directory labeled support with misc_patterns.te or 
file_patterns.te. 

I think the use of constraints should be increased as a way to "assert" 
the policy writer is doing the right thing.    So removing the 
assertions, because we have other places where we don't use constraints 
is an invalid argument.  Lets define assertions there and stop policy 
writers from doing

allow mydomain_t etc_t:file rw_file_perms

and other clearly security problematic code.


--
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:[~2007-05-03 13:12 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-04-27 22:24 Patch to cleanup audit handling in policy Daniel J Walsh
2007-04-27 23:38 ` Steve G
2007-04-30 14:17   ` Christopher J. PeBenito
2007-04-30 14:25     ` Daniel J Walsh
2007-04-30 14:39       ` Christopher J. PeBenito
2007-04-30 14:55         ` Daniel J Walsh
2007-04-30 15:29           ` Christopher J. PeBenito
2007-04-30 15:36             ` Daniel J Walsh
2007-04-30 17:04               ` Christopher J. PeBenito
2007-04-30 14:59     ` Steve G
2007-04-30 16:53       ` Christopher J. PeBenito
2007-05-01  0:49         ` Karl MacMillan
2007-05-01 13:31           ` Christopher J. PeBenito
2007-05-01 15:21             ` Karl MacMillan
2007-05-02 17:08               ` Christopher J. PeBenito
2007-05-02 17:18                 ` Karl MacMillan
2007-05-03 12:17                   ` Christopher J. PeBenito
2007-05-03 13:11                     ` Daniel J Walsh [this message]
2007-05-03 21:16                     ` Karl MacMillan

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=4639DF9E.70405@redhat.com \
    --to=dwalsh@redhat.com \
    --cc=cpebenito@tresys.com \
    --cc=kmacmillan@mentalrootkit.com \
    --cc=linux_4ever@yahoo.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.