netdev - Re: [RFC][PATCH 3/3] IPv4:Check IP_MULTICAST

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: <20080610.174202.32087382.yoshfuji@linux-ipv6.org>
Date:	Tue, 10 Jun 2008 17:42:02 +0900 (JST)
From:	YOSHIFUJI Hideaki / 吉藤英明 
	<yoshfuji@...ux-ipv6.org>
To:	shanwei@...fujitsu.com
Cc:	davem@...emloft.net, netdev@...r.kernel.org,
	yoshfuji@...ux-ipv6.org
Subject: Re: [RFC][PATCH 3/3] IPv4:Check IP_MULTICAST_LOOP option value

In article <484E3C0A.1000808@...fujitsu.com> (at Tue, 10 Jun 2008 16:32:10 +0800), Shan Wei <shanwei@...fujitsu.com> says:

> YOSHIFUJI Hideaki / 吉藤英明 写道:
> > In article <484E3293.8000507@...fujitsu.com> (at Tue, 10 Jun 2008 15:51:47 +0800), Shan Wei <shanwei@...fujitsu.com> says:
> > 
> >> The IP_MULTICAST_LOOP option can only be set with o or 1. When 
> >> other valuse are set, the kernel should return an error of EINVAL.
> >>
> >> In addition, the option should not be uesd by SOCK_STREAM type,
> >> same as IP_MULTICAST_IF, IP_MULTICAST_TTL.
> >>   
> >> But the kernel doesn't check them.
> > 
> > Is there any standard reference about this?
> > 
> I have not found it.
> But, the IP_MULTICAST_LOOP option is same as IPV6_MULTICAST_LOOP.

I disagree.
We follow what traditional BSDs do, and they do not check if the
value is 0 or 1 for IP_MULTICAST_LOOP.
On the other hand, they do for IPV6_MULTICAST_LOOP.

--yoshfuji
--
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