| 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: <AANLkTimf-FWCsiLqYDGg4nl-relRMuNvDowfTKZbe9kx@mail.gmail.com> Date: Mon, 3 May 2010 23:27:23 -0700 From: enh <enh@...gle.com> To: David Miller <davem@...emloft.net> Cc: brian.haley@...com, netdev@...r.kernel.org Subject: Re: linux kernel's IPV6_MULTICAST_HOPS default is 64; should be 1? On Mon, May 3, 2010 at 23:22, David Miller <davem@...emloft.net> wrote: > From: enh <enh@...gle.com> > Date: Mon, 3 May 2010 23:19:22 -0700 > >> for the *unicast* hops, a part of the RFC i didn't quote says: >> >> If the [IPV6_UNICAST_HOPS] option is not set, the >> system selects a default value. >> >> but for the *multicast* hops, which is what i'm talking about, this >> part of the quoted text seems pretty definitive: >> >> If IPV6_MULTICAST_HOPS is not set, the default is 1 >> (same as IPv4 today) >> >> this is what my test shows isn't true of linux; linux reuses its >> unicast default instead. > > Ok, I see, so yeah this needs to be fixed to use "1" instead of > "-1" in the np->xxx ipv6 socket initialization. i think so. there's already the IPV6_DEFAULT_MCASTHOPS constant defined to 1 but unused according to gitweb, so you might want to either use it or remove it. thanks! -- Elliott Hughes - http://who/enh - http://jessies.org/~enh/ -- 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