Skip to content

XFRM audit fixes/additions for net-2.6.25

Paul Moore linux-audit netdev 1 version Applied

Status from this message: Applied.

Get series with b4
b4 am [email protected]

Versions newest first

  1. v1 Latest3 patches 9 repliesApplied

Patches in v1 Applied

#Subject and filesSizeRepliesApplied
1/3XFRM: Assorted IPsec fixupsinclude/net/xfrm.h net/xfrm/xfrm_policy.c net/xfrm/xfrm_state.c+36 -462 replies
2/3XFRM: RFC4303 compliant auditinginclude/net/xfrm.h net/ipv4/ah4.c net/ipv4/esp4.c +7 more+184 -366 replies
3/3XFRM: Drop packets when replay counter would overflownet/xfrm/xfrm_output.c+4 -11 reply

Reviews trailers per patch

All 3 patches have a Reviewed-by or Acked-by.

PatchJames Morris
1/3A-b
2/3A-b
3/3A-b

Trailers given in replies are filled; those carried in the patches from earlier versions are outlined with dashes.

Read the v1 thread

Cover letter [PATCH 0/3] XFRM audit fixes/additions for net-2.6.25

Three patches backed against net-2.6.25 from today. Some of the audit messages are a little difficult to test by their nature but I've verified that I'm still able to send/receive IPsec protected traffic with the patches applied.

The first patch was posted before but David decided it best to split the patch so some parts could be pulled into 2.6.24; the patch was split and the 2.6.24 bits were accepted (the SPI byteorder fix) so patch #1 in the series is what is left for 2.6.25.

The second patch was posted before as an RFC patch without anyone complaining too loudly. Eric Paris made some suggestions about better handling of the "op=" audit field and I've tried to take that into account with this patch.

The final patch is the audit replay counter overflow issue fix that has been talked about on netdev. This sounded like the best course of action from the discussion but if I'm wrong, just drop this patch and I'll cook up something else to solve the problem.

Thanks.

--
paul moore
linux security @ hp