netdev - Re: [PATCH] XFRM: SPD auditing fix to include the netmask/prefix-length

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Thu, 29 Nov 2007 21:34:59 +1100
From:	Herbert Xu <herbert@...dor.apana.org.au>
To:	Paul Moore <paul.moore@...com>
Cc:	netdev@...r.kernel.org, linux-audit@...hat.com,
	Joy Latten <latten@...ibm.com>
Subject: Re: [PATCH] XFRM: SPD auditing fix to include the netmask/prefix-length

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?

Thanks,
-- 
Visit Openswan at http://www.openswan.org/
Email: Herbert Xu ~{PmV>HI~} <herbert@...dor.apana.org.au>
Home Page: http://gondor.apana.org.au/~herbert/
PGP Key: http://gondor.apana.org.au/~herbert/pubkey.txt
-
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html