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: <d16197a7-9564-42ce-8360-c22c7050ba12@6wind.com>
Date:   Thu, 17 Jan 2019 09:25:06 +0100
From:   Nicolas Dichtel <nicolas.dichtel@...nd.com>
To:     xiangxia.m.yue@...il.com, davem@...emloft.net,
        xiyou.wangcong@...il.com
Cc:     netdev@...r.kernel.org
Subject: Re: [PATCH RESEND net-next v2] net: ipv4: allocate ipv4_devconf
 memory for init_net

Le 16/01/2019 à 09:53, xiangxia.m.yue@...il.com a écrit :
> From: Tonghao Zhang <xiangxia.m.yue@...il.com>
> 
> The devconf setting on the init_net will affect other
> namespace when them created. For example:
> 
> $ cat /proc/sys/net/ipv4/conf/all/rp_filter
> 0
> $ echo 2 > /proc/sys/net/ipv4/conf/all/rp_filter
> $ cat /proc/sys/net/ipv4/conf/all/rp_filter
> 2
> 
> $ ip netns add ns100
> $ ip netns exec ns100 bash
> $ cat /proc/sys/net/ipv4/conf/all/rp_filter
> 2
> 
> The value of rp_filter in the ns100, should be 0 as
> default, but it is 2 same as _init_net_.
This problem has already been discussed in the past. We cannot change anymore
the current behavior, some users are relying on it.


Regards,
Nicolas

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ