From: Joy Latten <latten@austin.ibm.com>
To: Valdis.Kletnieks@vt.edu
Cc: netdev@vger.kernel.org, linux-audit@redhat.com, davem@davemloft.net
Subject: Re: [PATCH]: xfrm audit calls
Date: Wed, 12 Sep 2007 14:35:04 -0500 [thread overview]
Message-ID: <1189625704.15699.809.camel@faith.austin.ibm.com> (raw)
In-Reply-To: <30135.1189623401@turing-police.cc.vt.edu>
On Wed, 2007-09-12 at 14:56 -0400, Valdis.Kletnieks@vt.edu wrote:
> On Tue, 11 Sep 2007 19:03:14 CDT, Joy Latten said:
> > This patch modifies the current ipsec audit layer
> > by breaking it up into purpose driven audit calls.
> >
> > So far, the only audit calls made are when add/delete
> > an SA/policy.
>
> What other audit calls do you envision adding in the future?
Those specified in updated RFCs for ipsec, mainly 4301,
4302 and 4303.
Joy
prev parent reply other threads:[~2007-09-12 19:35 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-12 0:03 [PATCH]: xfrm audit calls Joy Latten
2007-09-12 8:57 ` David Miller
2007-09-12 18:56 ` Valdis.Kletnieks
2007-09-12 19:35 ` Joy Latten [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=1189625704.15699.809.camel@faith.austin.ibm.com \
--to=latten@austin.ibm.com \
--cc=Valdis.Kletnieks@vt.edu \
--cc=davem@davemloft.net \
--cc=linux-audit@redhat.com \
--cc=netdev@vger.kernel.org \
/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