netdev - Re: [PATCH] IPv6: Fix incorrect disable

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: <20090313.192448.155806143.davem@davemloft.net>
Date:	Fri, 13 Mar 2009 19:24:48 -0700 (PDT)
From:	David Miller <davem@...emloft.net>
To:	brian.haley@...com
Cc:	yoshfuji@...ux-ipv6.org, netdev@...r.kernel.org
Subject: Re: [PATCH] IPv6: Fix incorrect disable_ipv6 behavior

From: Brian Haley <brian.haley@...com>
Date: Fri, 13 Mar 2009 20:52:40 -0400

> Brian Haley wrote:
> > Fix the behavior of allowing both sysctl and addrconf_dad_failure()
> > to set the disable_ipv6 parameter without any bad side-effects.
> > If DAD fails and accept_dad > 1, we will still set disable_ipv6=1,
> > but then instead of allowing an RA to add an address then
> > immediately fail DAD, we simply don't allow the address to be
> > added in the first place.  This also lets the user set this flag
> > and disable all IPv6 addresses on the interface, or on the entire
> > system.
> 
> So I haven't seen an Ack/Nack for this patch, and the patchwork queue has shrunk
> to just a handful in the past few hours :)

It's near the top of my queue, I'm just debating what tree
to stick it into.

Probably I'll put it into net-next-2.6
--
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