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: <51C25878.2070302@cn.fujitsu.com>
Date:	Thu, 20 Jun 2013 09:18:48 +0800
From:	Gao feng <gaofeng@...fujitsu.com>
To:	David Miller <davem@...emloft.net>
CC:	ebiederm@...ssion.com, netdev@...r.kernel.org
Subject: Re: [PATCH v2 4/4] neigh: don't leak default parms to uninitial netns

On 06/20/2013 09:05 AM, David Miller wrote:
> From: Gao feng <gaofeng@...fujitsu.com>
> Date: Fri, 14 Jun 2013 10:06:47 +0800
> 
>> Only allow initial net namespace to get default parms
>> through netlink.
>>
>> Signed-off-by: Gao feng <gaofeng@...fujitsu.com>
> 
> Disallowing changes to the default neigh parms is fine, but there is no
> reason to forbid seeing what default neigh parms will be used in a given
> network namespace just because it isn't &init_net.
> 

Yes, we can make sure un-init net namespace can't do harm to default neigh parms,
it's enough.

> I don't see why you want to restrict this at all.
> 
> I'm not applying these patches, sorry.

You can just drop this one, are there some problems with the other 3 patches?
--
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

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ