linux-kernel - Re: sys_chroot+sys

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: <46FA35A6.1070400@davidnewall.com>
Date:	Wed, 26 Sep 2007 20:04:14 +0930
From:	David Newall <david@...idnewall.com>
To:	Al Viro <viro@....linux.org.uk>
CC:	Phillip Susi <psusi@....rr.com>,
	Alan Cox <alan@...rguk.ukuu.org.uk>,
	Bill Davidsen <davidsen@....com>, majkls <majkls@...pere.com>,
	bunk@...tum.de, linux-kernel@...r.kernel.org
Subject: Re: sys_chroot+sys_fchdir Fix

Al Viro wrote:
> Oh, for fsck sake...  Folks, it's standard-required behaviour.  Ability
> to chroot() implies the ability to break out of it.  Could we please
> add that (along with reference to SuS) to l-k FAQ and be done with that
> nonsense?

I'm pretty confident that it's only standard behavior for Linux.  Every 
other unix says it's not allowed.
-
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/