netdev - Is 64k bind patch making bad assumption?

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 for Android: free password hash cracker in your pocket

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

Date:	Mon, 2 Feb 2009 10:35:15 -0800
From:	Stephen Hemminger <shemminger@...tta.com>
To:	Evgeniy Polyakov <s0mbre@...rvice.net.ru>,
	David Miller <davem@...emloft.net>
Cc:	netdev@...r.kernel.org
Subject: Is 64k bind patch making bad assumption?

The patch to allow more that 64k connections is assuming that
all IP addresses on a machine have the same connectivity and policy.
I can think of several cases where this is not true:
  1. Server machine with public IP's for connections and private IP's
     for backend database connection
  2. Applications where certain IP's are required for security
     protocols
  3. Machines doing policy based routing

Doesn't this patch change/break this?
--
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