linux-kernel - Re: [PATCH] ipv4: in new netns initialize sysctls in net.ipv4.conf.* with defaults

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]

Date:	Thu, 25 Feb 2016 15:20:48 +0100
From:	Nicolas Dichtel <nicolas.dichtel@...nd.com>
To:	"Eric W. Biederman" <ebiederm@...ssion.com>,
	David Miller <davem@...emloft.net>
Cc:	khlebnikov@...dex-team.ru, netdev@...r.kernel.org,
	containers@...ts.linux-foundation.org, vvs@...tuozzo.com,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH] ipv4: in new netns initialize sysctls in net.ipv4.conf.*
 with defaults

Le 24/02/2016 23:05, Eric W. Biederman a écrit :
[snip]
> In the general case the current behavior is random and not something
> applications can count on, and we would do well to fix it so it is less
> random.  In particular consider the case of an application in a
> non-initial network namespace creating a new network namespace.  It is
> not even possible to predict what values they will get for sysctls
> today.
+1

>  From a backwards compatibility standpoint we are probably better off
> with copying from the current network namespace rather than the initial
> network namespace.  As that more closely resembles the common case
> today.
+1