From: Paul Moore <paul.moore@hp.com>
To: Herbert Xu <herbert@gondor.apana.org.au>
Cc: netdev@vger.kernel.org, linux-audit@redhat.com,
Joy Latten <latten@us.ibm.com>
Subject: Re: [PATCH] XFRM: SPD auditing fix to include the netmask/prefix-length
Date: Thu, 29 Nov 2007 08:45:46 -0500 [thread overview]
Message-ID: <200711290845.46623.paul.moore@hp.com> (raw)
In-Reply-To: <20071129103459.GD22537@gondor.apana.org.au>
On Thursday 29 November 2007 5:34:59 am Herbert Xu wrote:
> On Mon, Nov 26, 2007 at 07:55:12PM +0000, Paul Moore wrote:
> > Currently the netmask/prefix-length of an IPsec SPD entry is not included
> > in any of the SPD related audit messages. This can cause a problem when
> > the audit log is examined as the netmask/prefix-length is vital in
> > determining what network traffic is affected by a particular SPD entry.
> > This patch fixes this problem by adding two additional fields,
> > "src_prefixlen" and "dst_prefixlen", to the SPD audit messages to
> > indicate the source and destination netmasks. These new fields are only
> > included in the audit message when the netmask/prefix-length is less than
> > the address length, i.e. the SPD entry applies to a network address and
> > not a host address.
>
> Any reason why we don't just always include them?
The audit folks seem to be very sensitive to the size/length of the audit
messages, they prefer they be as small as possible. I thought that one way
to save space would be to only print the prefix length information when the
address referred to a network and not a single host.
Would you prefer it if the prefix length information was always included in
the audit message? Joy? Audit folks?
--
paul moore
linux security @ hp
next prev parent reply other threads:[~2007-11-29 13:45 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-26 19:55 [PATCH] XFRM: SPD auditing fix to include the netmask/prefix-length Paul Moore
2007-11-29 10:34 ` Herbert Xu
2007-11-29 13:45 ` Paul Moore [this message]
2007-11-30 14:51 ` Paul Moore
2007-11-30 15:16 ` Joy Latten
2007-12-01 12:28 ` Herbert Xu
2007-12-03 4:52 ` Paul Moore
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=200711290845.46623.paul.moore@hp.com \
--to=paul.moore@hp.com \
--cc=herbert@gondor.apana.org.au \
--cc=latten@us.ibm.com \
--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 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.