linux-kernel - Re: [patch net-next 3/5] ipv6: consider net.ipv6.conf.all sysctls when making decisions

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: <20140610101334.565bc484@nehalam.linuxnetplumber.net>
Date:	Tue, 10 Jun 2014 10:13:34 -0700
From:	Stephen Hemminger <stephen@...workplumber.org>
To:	Milos Vyletel <milos.vyletel@...il.com>
Cc:	davem@...emloft.net, amwang@...hat.com, netdev@...r.kernel.org,
	Oliver Neukum <oliver@...kum.org>,
	Alexey Kuznetsov <kuznet@....inr.ac.ru>,
	James Morris <jmorris@...ei.org>,
	Hideaki YOSHIFUJI <yoshfuji@...ux-ipv6.org>,
	Patrick McHardy <kaber@...sh.net>,
	Pravin B Shelar <pshelar@...ira.com>,
	Nicolas Dichtel <nicolas.dichtel@...nd.com>,
	Mike Rapoport <mike.rapoport@...ellosystems.com>,
	Daniel Borkmann <dborkman@...hat.com>,
	Or Gerlitz <ogerlitz@...lanox.com>,
	Tom Herbert <therbert@...gle.com>,
	Hannes Frederic Sowa <hannes@...essinduktion.org>,
	Florent Fourcot <florent.fourcot@...t-bretagne.fr>,
	Eric Dumazet <edumazet@...gle.com>,
	Paul Durrant <Paul.Durrant@...rix.com>,
	linux-usb@...r.kernel.org (open list:USB CDC ETHERNET...),
	linux-kernel@...r.kernel.org (open list)
Subject: Re: [patch net-next 3/5] ipv6: consider net.ipv6.conf.all sysctls
 when making decisions

On Tue, 10 Jun 2014 12:19:11 -0400
Milos Vyletel <milos.vyletel@...il.com> wrote:

> As it is right now net.ipv6.conf.all.* are mostly ignored and instead
> we're only making decisions based on interface specific settings. These
> settings are coppied from net.ipv6.conf.default and changing either all
> or default settings have no effect.

Although this is the right idea conceptually, it risks creating unhappy
users because it changes the semantics of the API. This will probably break
somebody's configuration.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/