netdev - [PATCHv3 net-next 0/3] IPComp fixes

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-next>] [day] [month] [year] [list]

Date:	Mon, 16 Dec 2013 18:47:47 +0800
From:	Fan Du <fan.du@...driver.com>
To:	<steffen.klassert@...unet.com>
CC:	<davem@...emloft.net>, <netdev@...r.kernel.org>
Subject: [PATCHv3 net-next 0/3] IPComp fixes

Hi,

This patchset includes bug fix focusing on IPComp mainly, which addresses
IPComp Compression Parameter Index(CPI, 16bits of 32bits SPI value) problem.

And other issue is the compression part, undesirable packet will not be
compressed, and then send into wire, this packet will be dropped by policy
checking in the receiver side.

v2:
  Patch1: Clean up align issue from v1.
  Patch2: Introduce verify_userspi_info for pkfey and netlink interface
          to share code.
  Patch3: Add Documentation/networking/ipsec.txt to document known issues. 

v3:
  Patch2: Fix while space error.
  Patch3: Del empty line

Fan Du (3):
  xfrm: check user specified spi for IPComp
  xfrm: export verify_userspi_info for pkfey and netlink interface
  xfrm: Add file to document IPsec corner case

 Documentation/networking/ipsec.txt |   38 ++++++++++++++++++++++++++++++++++++
 include/net/xfrm.h                 |    1 +
 net/key/af_key.c                   |    6 ++++++
 net/xfrm/xfrm_state.c              |   24 +++++++++++++++++++++++
 net/xfrm/xfrm_user.c               |   29 ++++-----------------------
 5 files changed, 73 insertions(+), 25 deletions(-)
 create mode 100644 Documentation/networking/ipsec.txt

-- 
1.7.9.5

--
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