From: David Miller <davem@davemloft.net>
To: paul.moore@hp.com
Cc: netdev@vger.kernel.org, linux-audit@redhat.com, latten@austin.ibm.com
Subject: Re: [PATCH 1/2] XFRM: RFC4303 compliant auditing
Date: Fri, 21 Dec 2007 14:58:38 -0800 (PST) [thread overview]
Message-ID: <20071221.145838.17444757.davem@davemloft.net> (raw)
In-Reply-To: <20071221141454.11660.83572.stgit@flek.lan>
From: Paul Moore <paul.moore@hp.com>
Date: Fri, 21 Dec 2007 09:14:55 -0500
> This patch adds a number of new IPsec audit events to meet the auditing
> requirements of RFC4303. This includes audit hooks for the following events:
>
> * Could not find a valid SA [sections 2.1, 3.4.2]
> . xfrm_audit_state_notfound()
> . xfrm_audit_state_notfound_simple()
>
> * Sequence number overflow [section 3.3.3]
> . xfrm_audit_state_replay_overflow()
>
> * Replayed packet [section 3.4.3]
> . xfrm_audit_state_replay()
>
> * Integrity check failure [sections 3.4.4.1, 3.4.4.2]
> . xfrm_audit_state_icvfail()
>
> While RFC4304 deals only with ESP most of the changes in this patch apply to
> IPsec in general, i.e. both AH and ESP. The one case, integrity check
> failure, where ESP specific code had to be modified the same was done to the
> AH code for the sake of consistency.
>
> Signed-off-by: Paul Moore <paul.moore@hp.com>
Applied.
next prev parent reply other threads:[~2007-12-21 22:58 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-21 14:14 [PATCH 0/2] XFRM auditing patch rebased Paul Moore
2007-12-21 14:14 ` [PATCH 1/2] XFRM: RFC4303 compliant auditing Paul Moore
2007-12-21 22:58 ` David Miller [this message]
2007-12-21 14:15 ` [PATCH 2/2] XFRM: Drop packets when replay counter would overflow Paul Moore
2007-12-21 22:59 ` David Miller
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=20071221.145838.17444757.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=latten@austin.ibm.com \
--cc=linux-audit@redhat.com \
--cc=netdev@vger.kernel.org \
--cc=paul.moore@hp.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;
as well as URLs for NNTP newsgroup(s).