public inbox for linux-audit@redhat.com
 help / color / mirror / Atom feed
From: Steve Grubb <sgrubb@redhat.com>
To: linux-audit@redhat.com
Subject: Re: [PATCH 1/2] add SIGNAL syscall class
Date: Wed, 14 Feb 2007 14:04:07 -0500	[thread overview]
Message-ID: <200702141404.07353.sgrubb@redhat.com> (raw)
In-Reply-To: <20070214182431.GA17337@fc.hp.com>

On Wednesday 14 February 2007 13:24:31 Amy Griffis wrote:
> Add a syscall class for sending signals.

The intent of the syscall classes had been to make an update independent way 
of being able to specify audit rules for filesystem auditing where new 
syscalls could be added. I don't know if this grouping would be useful in 
practice. <shrug>

What I have been thinking about is a grouping for delete and close. That would 
align with requirements on security standards people have to meet.

-Steve

  parent reply	other threads:[~2007-02-14 19:04 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-02-14 18:24 [PATCH 1/2] add SIGNAL syscall class Amy Griffis
2007-02-14 18:25 ` [PATCH 2/2] audit signal recipients Amy Griffis
2007-02-14 19:04 ` Steve Grubb [this message]
2007-02-14 20:12   ` [PATCH 1/2] add SIGNAL syscall class Amy Griffis
2007-02-14 20:32     ` Steve Grubb
2007-02-14 21:38       ` Amy Griffis

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=200702141404.07353.sgrubb@redhat.com \
    --to=sgrubb@redhat.com \
    --cc=linux-audit@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