All of lore.kernel.org
 help / color / mirror / Atom feed
From: David Caplan <dac@tresys.com>
To: Steve G <linux_4ever@yahoo.com>
Cc: David Slater <ds@hypertechsystems.com>, selinux@tycho.nsa.gov
Subject: Re: auditctl examples?
Date: Wed, 08 Feb 2006 10:25:54 -0500	[thread overview]
Message-ID: <43EA0D82.3020109@tresys.com> (raw)
In-Reply-To: <20060208145708.49043.qmail@web51512.mail.yahoo.com>

Steve G wrote:
>> You said you are interested in using auditctl to do your auditing, but 
>> you can also get what you want with selinux policy.
> 
> This is true, but I wouldn't recommend that. Its too easy to make a typo and
> cause unexpected problems later. In general, people should never need to modify
> policy. It makes too many support problems when everyone has tweeked their
> policy.
> 

I suggested it because you stated in your response that auditctl does 
not support exactly what he wants to do. I agree with you that in 
general people should not have to modify their policy directly. I do 
think it is appropriate to "tweek" the policy when you have a specific 
protection/security requirement that is not addressed by the standard 
policy.

-- 
__________________________________

David Caplan     410 290 1411 x105
dac@tresys.com
Tresys Technology, LLC
8840 Stanford Blvd., Suite 2100
Columbia, MD 21045

--
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-02-08 15:28 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-02-07 20:25 auditctl examples? David Slater
2006-02-07 22:26 ` Steve G
2006-02-08 14:02 ` David Caplan
2006-02-08 14:57   ` Steve G
2006-02-08 15:25     ` David Caplan [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=43EA0D82.3020109@tresys.com \
    --to=dac@tresys.com \
    --cc=ds@hypertechsystems.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.