netdev - Re: [PATCH net-2.6.25 1/3]sysctl: make the sys.net.core sysctls per-namespace

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] [day] [month] [year] [list]

Message-Id: <20071208.001038.256039822.davem@davemloft.net>
Date:	Sat, 08 Dec 2007 00:10:38 -0800 (PST)
From:	David Miller <davem@...emloft.net>
To:	xemul@...nvz.org
Cc:	netdev@...r.kernel.org, containers@...ts.osdl.org, devel@...nvz.org
Subject: Re: [PATCH net-2.6.25 1/3]sysctl: make the sys.net.core sysctls
 per-namespace

From: Pavel Emelyanov <xemul@...nvz.org>
Date: Fri, 07 Dec 2007 16:07:19 +0300

> Making them per-namespace is required for the following 
> two reasons:
> 
>  First, some ctl values have a per-namespace meaning.
>  Second, making them writable from the sub-namespace
>  is an isolation hole.
> 
> So I introduce the pernet operations to create these
> tables. For init_net I use the existing statically
> declared tables, for sub-namespace they are duplicated
> and the write bits are removed from the mode.
> 
> Signed-off-by: Pavel Emelyanov <xemul@...nvz.org>

Applied to net-2.6.25, but I fear you're going to need to do something
similar for ipv4, ipv6, and who knows what other protocols.  And as a
result we'll end up with all kinds of protocol specific things in the
net namespace structure which totally stinks.

Such things will need to be registered dynamically just like the
protocols themselves are into the kernel.
--
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