linux-kernel - Re: Add IPSec IP Range in Linux kernel

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]

Message-Id: <20111108.121620.2044664919065812135.davem@davemloft.net>
Date:	Tue, 08 Nov 2011 12:16:20 -0500 (EST)
From:	David Miller <davem@...emloft.net>
To:	adobriyan@...il.com
Cc:	peter.p.waskiewicz.jr@...el.com, danila.st@...l.ru,
	linux-kernel@...r.kernel.org, netdev@...r.kernel.org,
	linux-crypto@...r.kernel.org, linux-security-module@...r.kernel.org
Subject: Re: Add IPSec IP Range in Linux kernel

From: Alexey Dobriyan <adobriyan@...il.com>
Date: Tue, 8 Nov 2011 14:08:24 +0200

> changing addr_match() is trivial for ipv4 and easy for ipv6. :-)

No, this is not happening.  This added complexity screws up all the hash table
and lookup optimizations we have in the XFRM layer.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/