'chroot_safe' is a alternative method for chrooting dynamically linked applications. It delays the chrooting until after dynamic linking has completed, so you don't need to have a copy of the binary or libraries within the chroot. This simplifies the process of chrooting an application, as you often do not need any files besides the data files within the chroot. In addition to chrooting the application, 'chroot_safe' also drops root privileges before letting the application start.
released on 9 April 2005
|License||Verified by||Verified on||Notes|
|X11||Janet Casey||15 June 2004|
Leaders and contributors
Resources and communication
|Developer||VCS Repository Webview||http://sourceforge.net/cvs/?group_id=110671|
This entry (in part or in whole) was last reviewed on 21 January 2017.
Permission is granted to copy, distribute and/or modify this document under the terms of the GNU Free Documentation License, Version 1.3 or any later version published by the Free Software Foundation; with no Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. A copy of the license is included in the page “GNU Free Documentation License”.
The copyright and license notices on this page only apply to the text on this page. Any software or copyright-licenses or other similar notices described in this text has its own copyright notice and license, which can usually be found in the distribution or license text itself.