Linux-audit Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Marcus Meissner <meissner@suse.de>
To: Steve Grubb <sgrubb@redhat.com>
Cc: linux-audit@redhat.com, Clif Flynt <clif@cflynt.com>
Subject: Re: New List Member: Intro & comments
Date: Mon, 7 Aug 2006 11:37:33 +0200	[thread overview]
Message-ID: <20060807093731.GD10031@suse.de> (raw)
In-Reply-To: <200607311354.30484.sgrubb@redhat.com>

On Mon, Jul 31, 2006 at 01:54:30PM -0400, Steve Grubb wrote:
> On Monday 31 July 2006 13:14, Clif Flynt wrote:
> 
> > As I read things, AppArmor doesn't support the file audit
> > requirements, but Auditd can meet the DSS requirements.
> 
> Its not the responsibility of the access control mechanism to support audit. 
> Audit has its own kernel patches for this. I don't know if Suse picked up 
> those patches since yhey are in the upcoming 2.6.18 kernel.

We will likely do this later (with a SLES 10 Service Pack) to reach CAPP
compliance.

Ciao, Marcus

  reply	other threads:[~2006-08-07  9:37 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-07-31 17:14 New List Member: Intro & comments Clif Flynt
2006-07-31 17:54 ` Steve Grubb
2006-08-07  9:37   ` Marcus Meissner [this message]
2006-07-31 20:05 ` SQLite Clarification Clif Flynt
2006-07-31 21:13   ` Steve Grubb
2006-08-02 20:49     ` auditctl question Lane Williams
2006-08-02 22:03       ` Steve Grubb
2006-08-02 22:15         ` Linda Knippers
2006-08-02 22:29           ` Steve Grubb
2006-08-03  0:22       ` Klaus Weidner
2006-08-03 13:00         ` Williams, P. Lane
2006-08-03 15:18           ` Klaus Weidner
2006-08-03 20:02             ` Williams, P. Lane
2006-08-03 20:29               ` Klaus Weidner
2006-08-03 21:06               ` Steve Grubb
2006-08-04  1:50                 ` Williams, P. Lane
2006-08-04 10:28                   ` Steve Grubb
2006-08-04 12:48                     ` Lane Williams
2006-07-31 22:05   ` SQLite Clarification Clif Flynt

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=20060807093731.GD10031@suse.de \
    --to=meissner@suse.de \
    --cc=clif@cflynt.com \
    --cc=linux-audit@redhat.com \
    --cc=sgrubb@redhat.com \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox