linux-kernel - 2.6.18 - check for chroot, broken root and cwd values in procfs

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 for Android: free password hash cracker in your pocket

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Message-ID: <20061012140224.GA7632@wavehammer.waldi.eu.org>
Date:	Thu, 12 Oct 2006 16:02:24 +0200
From:	Bastian Blank <bastian@...di.eu.org>
To:	linux-kernel@...r.kernel.org,
	"Eric W. Biederman" <ebiederm@...ssion.com>,
	Andrew Morton <akpm@...l.org>,
	Linus Torvalds <torvalds@...l.org>
Cc:	md@...ux.it
Subject: 2.6.18 - check for chroot, broken root and cwd values in procfs

Hi folks

The commit 778c1144771f0064b6f51bee865cceb0d996f2f9 replaced the old
root-based security checks in procfs with processed based ones.

This makes the old check for chroot "[ -r /proc/1/root ]" unusable as
readlink on it now always succedds. Also it provides buggy values inside
a chroot, both /proc/1/root and /proc/self/root points to / but in real
they are different.

Is this a desired output or can I call this a bug? If the behaviour is
correct, is there a replacement for this check?

Bastian

-- 
Behind every great man, there is a woman -- urging him on.
		-- Harry Mudd, "I, Mudd", stardate 4513.3

Download attachment "signature.asc" of type "application/pgp-signature" (198 bytes)