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: <20100504.143824.82823095.davem@davemloft.net> Date: Tue, 04 May 2010 14:38:24 -0700 (PDT) From: David Miller <davem@...emloft.net> To: brian.haley@...com Cc: dlstevens@...ibm.com, enh@...gle.com, netdev@...r.kernel.org, netdev-owner@...r.kernel.org Subject: Re: linux kernel's IPV6_MULTICAST_HOPS default is 64; should be 1? From: Brian Haley <brian.haley@...com> Date: Tue, 04 May 2010 10:40:58 -0400 > Not exactly. It fixes the case where it's wrong by default, but > the corner case of setting it to -1 via setsockopt() says: > > x == -1: use kernel default > > But that will revert back to the kernel using 64 on the next transmit. > I can work on an update to this that makes a new mcast_hops per-interface > setting and makes ip6_dst_hoplimit() aware of it. Or even easier, just > have setsockopt() trap the -1 and set np->mcast_hops to 1. Built but > untested patch below. I thought that we agreed that when the user explicitly asks for "-1" it should get the behavior right now, with is to use ip6_dst_hoplimit()? I think I even acknowledged when Elliot mentioned this explicitly, and I think it's a good idea. -- 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