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  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]
Date:	Mon, 01 Oct 2007 20:49:21 +0900 (JST)
From:	YOSHIFUJI Hideaki / 吉藤英明 
To:	brian.haley@...comy,
Subject: Re: [IPV6] Fix ICMPv6 redirect handling with target multicast


In article <> (at Sat, 29 Sep 2007 10:04:48 +0900 (JST)), YOSHIFUJI Hideaki / 吉藤英明 <> says:

> In article <> (at Fri, 28 Sep 2007 17:50:38 -0700), David Stevens <> says:
> > Brian,
> >         A multicast address should never be the target of a neighbor
> > discovery request; the sender should use the mapping function for all
> > multicasts. So, I'm not sure that your example can ever happen, and it
> > certainly is ok to send ICMPv6 errors to multicast addresses in general.
> > But I don't see that it hurts anything. either (since it should never 
> > happen :-)),
> > so I don't particularly object, either.
> >         I think it'd also be better if you add the check to be:
> > 
> >         if (ipv6_addr_type(target) & 
> > 
> > or something along those lines, rather than reproducing ipv6_addr_type() 
> > code
> > separately in a new ipv6_addr_linklocal() function.

I'm fine with the idea of the fix itself.

Please use ipv6_addr_type() so far and convert other users as well
to ipv6_addr_linklocal() in another patch.



To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to
More majordomo info at

Powered by blists - more mailing lists