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  PHC 
Open Source and information security mailing list archives
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Date:	Thu, 5 Jun 2008 22:14:10 +0200
From:	Thomas Graf <>
To:	"YOSHIFUJI Hideaki / ?$B5HF#1QL@" <>
Subject: Re: [PATCH] ipv6 addrconf: Ignore requests to set NODAD flag when changing addresses

* YOSHIFUJI Hideaki / ?$B5HF#1QL@ <> 2008-06-05 23:32
> In article <> (at Thu, 5 Jun 2008 11:04:47 +0200), Thomas Graf <> says:
> > * YOSHIFUJI Hideaki <> 2008-06-05 11:53
> > > And well, it does not take effect so far, but 
> > > DAD after link failure logic is planned in long term.
> > > So current code is okay to me.
> > 
> > Alright, that makes sense if that code ever is written.
> > 
> > I'm not sure I understand your new patch though, why do you want to
> > disable setting the nodad flag for new addresses nowW?
> If we should really need to avoid the confusion, we have an option
> to disallow modification of NODAD flag so far with the patch I've posted.
> But anyway, I'm going to leave it as-is if you are okay.

Your patch would have disabled the ability to even add new addresses
with the NODAD flag set, that's what confused me. I'm fine with
leaving everything as-is since you explained that DAD will be done
after link failures in the future.
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