All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Christopher J. PeBenito" <cpebenito@tresys.com>
To: Steve G <linux_4ever@yahoo.com>
Cc: Daniel J Walsh <dwalsh@redhat.com>, SE Linux <selinux@tycho.nsa.gov>
Subject: Re: Patch to cleanup audit handling in policy.
Date: Mon, 30 Apr 2007 14:17:30 +0000	[thread overview]
Message-ID: <1177942650.3570.78.camel@sgc> (raw)
In-Reply-To: <254813.17034.qm@web51501.mail.re2.yahoo.com>

On Fri, 2007-04-27 at 16:38 -0700, Steve G wrote:
> >I have removed -send_audit_msgs_pattern and replaced it with 4 functions 
> 
> I'd like to clarify what they are in case anyone thinks the names need tweeking
> 
> logging_send_audit_msg - This is for any Trusted App that needs to send audit
> events
> 
> logging_set_loginuid - This would be for entry point daemons or daemons that
> perform actions on behalf of a user (cron/at). Includes the ability to send audit
> events.
> 
> logging_set_audit - This should be for the audit daemon only
> 
> logging_set_auditctl - This is only for auditctl and autrace.

I'm not convinced that these are necessary.  The assertions in the
policy are mainly to stop people from accidentally shooting themselves
in the foot by allowing potentially dangerous access, for example,
access to /etc/shadow or raw disk access.

-- 
Chris PeBenito
Tresys Technology, LLC
(410) 290-1411 x150


--
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-04-30 14:18 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 [this message]
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
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=1177942650.3570.78.camel@sgc \
    --to=cpebenito@tresys.com \
    --cc=dwalsh@redhat.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.