linux-kernel - Re: [PATCH] [RFC] Make it easier to harden /proc/

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: <201103162204.00031.arnd@arndb.de>
Date:	Wed, 16 Mar 2011 22:03:59 +0100
From:	Arnd Bergmann <arnd@...db.de>
To:	Richard Weinberger <richard@....at>
Cc:	Kees Cook <kees.cook@...onical.com>, linux-kernel@...r.kernel.org,
	akpm@...ux-foundation.org, serge@...lyn.com, eparis@...hat.com,
	jmorris@...ei.org, eugeneteo@...nel.org, drosenberg@...curity.com,
	"Eric W. Biederman" <ebiederm@...ssion.com>
Subject: Re: [PATCH] [RFC] Make it easier to harden /proc/

On Wednesday 16 March 2011 21:52:49 Richard Weinberger wrote:
> Am Mittwoch 16 März 2011, 21:45:45 schrieb Arnd Bergmann:
> > How does this interact with the per-namespace sysctls that Eric
> > Biederman added a few years ago?
> 
> Do you mean CONFIG_{UTS, UPC, USER, NET,}_NS?

I mean specifically e51b6ba07 "sysctl: Infrastructure for per namespace sysctls"
and related patches. I've looked a bit closer there and it seems that
this is only used for network namespaces at the moment.

> > I had expected that any dangerous sysctl would not be visible in
> > an unpriviledge container anyway.
> 
> No way.
> That's why it's currently a very good idea to mount /proc/ read-only into a container.

Ok, I see. 

	Arnd
--
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/