netdev - [PATCH][IPSEC][0/6] fix conflict of device tunnels with the ipsec tunnel

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:	Thu, 8 Feb 2007 17:03:24 +0900
From:	Kazunori MIYAZAWA <kazunori@...azawa.org>
To:	Herbert Xu <herbert@...dor.apana.org.au>,
	David Miller <davem@...emloft.net>
Cc:	Miika Komu <miika@....fi>, Diego Beltrami <Diego.Beltrami@...t.fi>,
	netdev@...r.kernel.org, usagi-core@...ux-ipv6.org
Subject: [PATCH][IPSEC][0/6] fix conflict of device tunnels with the ipsec
 tunnel

Hello David and Herbert,

Thank you for applying our patches with the fix.

I send patches to fix conflict of device tunnels with the inter
address family ipsec tunnel. Yoshifuji-san and Kozakai-san
noticed me of the confliction.

I adopt same approach of tunnel4.c and tunnel6.c. I extend them
to support inter address family.

We need this to use ipcomp with inter address family tunnel.

[1/6] extending xfrm4_tunnel utility to support inter address family for "sit"
[2/6] extending xfrm6_tunnel utility to support inter address family
[3/6] fix to refer encap_family when comparing the kernel generated xfrm_state
[4/6] changing "ipip tunnel" and xfrm4_tunnel to the API
[5/6] changing "ip6_tunnel" and xfrm6_tunnel to the API
[6/6] make "sit tunnel" use xfrm4_tunnel_register 

Best regards,

--
Kazunori Miyazawa

-
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