| 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: <4C76DA62.8040109@candelatech.com> Date: Thu, 26 Aug 2010 14:19:30 -0700 From: Ben Greear <greearb@...delatech.com> To: David Miller <davem@...emloft.net> CC: brian.haley@...com, netdev@...r.kernel.org Subject: Re: [net-next] ipv6: Enable netlink notification for tentative addresses. On 08/26/2010 01:18 PM, David Miller wrote: > From: Brian Haley<brian.haley@...com> > Date: Thu, 26 Aug 2010 15:57:51 -0400 > >> But then we get a message for an address that can't be used because >> it hasn't passed DAD, I'm not so sure that is a good thing, >> especially if we don't get notified when it passes DAD. > > I think that we shouldn't send notifications for an address that can't > even be used. So essentially I argue against this patch in any form :) In our case, we enable IPv6 in user-space, and then we want to get some immediate indication that indeed the process is working as expected. In other cases, we want to remove all IPv6 addresses, so if we have not even been notified that the IP exists, then we cannot know how to delete it. In my patch, we still get the update when DAD completes, so applications can take note of the flags if they care about the details. We've been running this patch for several years, and it has not caused any obvious problems with other tools, so I think it's safe enough. Thanks, Ben -- Ben Greear <greearb@...delatech.com> Candela Technologies Inc http://www.candelatech.com -- 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