All of lore.kernel.org
 help / color / mirror / Atom feed
From: Amy Griffis <amy.griffis@hp.com>
To: linux-audit@redhat.com
Subject: Re: [PATCH 1/2] add SIGNAL syscall class
Date: Wed, 14 Feb 2007 15:12:05 -0500	[thread overview]
Message-ID: <20070214201205.GA18196@fc.hp.com> (raw)
In-Reply-To: <200702141404.07353.sgrubb@redhat.com>

Steve Grubb wrote:  [Wed Feb 14 2007, 02:04:07PM EST]
> 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.

Yeah, I know I used it in a different way from the original purpose.
But I think this is still a valid use... When we are adding or
removing a rule, we need a way to determine if the rule specified one
of the syscalls for sending signals.

> I don't know if this grouping would be useful in practice. <shrug>

Yeah I wasn't sure either, so I didn't add the filtering part.

> 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.

Makes sense. Do you think we're in danger of running out of slots for
syscall classes?

Amy

  reply	other threads:[~2007-02-14 20:12 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 ` [PATCH 1/2] add SIGNAL syscall class Steve Grubb
2007-02-14 20:12   ` Amy Griffis [this message]
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=20070214201205.GA18196@fc.hp.com \
    --to=amy.griffis@hp.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 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.