linux-kernel - Re: Chroot bug

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: <46FA3D4B.20805@davidnewall.com>
Date:	Wed, 26 Sep 2007 20:36:51 +0930
From:	David Newall <david@...idnewall.com>
To:	Alan Cox <alan@...rguk.ukuu.org.uk>
CC:	"Serge E. Hallyn" <serge@...lyn.com>,
	Bill Davidsen <davidsen@....com>,
	Philipp Marek <philipp@...ek.priv.at>, 7eggert@....de,
	majkls <majkls@...pere.com>, bunk@...tum.de,
	linux-kernel@...r.kernel.org
Subject: Re: Chroot bug

Alan Cox wrote:
>>> The dot-dot entry in the root directory is interpreted to mean the 
>>> root directory itself. Thus, dot-dot cannot be used to access files 
>>> outside the subtree rooted at the root directory.
>>>       
>
> Which is behaviour chroot preserves properly.
>   

And yet it is the dot-dot entry which is used to access files outside 
the root.

> The specification says explicitly
>
> 	"The process working directory is unaffected by chroot()."
>   

Do you believe that when those words were first written, the hidden 
conflict, namely that it permits dot-dot to access files outside the 
subtree, was understood?  They would have said so if that were the case.
-
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/