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 for Android: free password hash cracker in your pocket
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:	Fri, 08 Apr 2016 16:18:29 +0200
From:	Bjørn Mork <bjorn@...k.no>
To:	Daniel Borkmann <daniel@...earbox.net>
Cc:	davem@...emloft.net, hannes@...essinduktion.org,
	robbat2@...too.org, netdev@...r.kernel.org
Subject: Re: [PATCH net-next] ipv6, token: allow for clearing the current device token

Daniel Borkmann <daniel@...earbox.net> writes:

>  
>  	if (!token)
>  		return -EINVAL;
> -	if (ipv6_addr_any(token))
> -		return -EINVAL;
>  	if (dev->flags & (IFF_LOOPBACK | IFF_NOARP))
>  		return -EINVAL;

Not directly related to the patch in question.  It just made me aware of
this restriction...

I realize that I'm a few years late here, but what's with the IFF_NOARP?
Is that just because we can't do DAD for the token based addresses?  How
is that different from manually configuring the whole address?



Bjørn

Powered by blists - more mailing lists