| 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
| ||
|
Message-Id: <20120612.152651.979001082972454031.davem@davemloft.net> Date: Tue, 12 Jun 2012 15:26:51 -0700 (PDT) From: David Miller <davem@...emloft.net> To: nhorman@...driver.com Cc: netdev@...r.kernel.org Subject: Re: [PATCHv2 net-next] ipv4: Add interface option to enable routing of 127.0.0.0/8 From: Neil Horman <nhorman@...driver.com> Date: Tue, 12 Jun 2012 08:32:38 -0400 > On Tue, Jun 12, 2012 at 07:31:15AM -0400, Thomas Graf wrote: >> On Tue, Jun 12, 2012 at 07:14:44AM -0400, Neil Horman wrote: >> > Just out of curiosity, would it be more efficient to implement this by >> > optionally adding a prohibit route to the local table for 127.0.0.0/8 to every >> > interface that was brought up, based on weather or not that interfaces >> > route_localnet bool was true or not? It would save the additional checks in the >> > routing path I think. Not sure how much a savings that is, but I thought I >> > would ask. >> >> It's not that simple because we also use the local table for source >> address selection and local address verification. So we would have to >> exclude/include such routes conditionally based on some route lookup >> purpose indicator. Such a prohibit route would have to be valid only >> in the output context. > > ah, understood, so that doesn't really save us anything, it just moves the point > at which we do the check. > > Acked-by: Neil Horman <nhorman@...driver.com> Applied, thanks guys. -- 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
Powered by blists - more mailing lists