summaryrefslogtreecommitdiff
path: root/README
diff options
context:
space:
mode:
authorRoger Leigh <rleigh@debian.org>2006-07-29 17:29:37 +0000
committerRoger Leigh <rleigh@debian.org>2006-07-29 17:29:37 +0000
commit1b3b7511596ea3cd5212ad61bc48ca884fd1d088 (patch)
tree5a39c528adef55688210ee9874e196ea47f45584 /README
parent262b335161988f529328a748e5fe8072b24fb324 (diff)
downloadschroot-1b3b7511596ea3cd5212ad61bc48ca884fd1d088.tar.gz
* Update manual pages.
* sbuild/sbuild-lock.h: Add missing virtual specifier from virtual methods in derived lock classes. * sbuild/sbuild-session.cc: Remove use of excess braces when throwing exceptions. (get_shell): Use log_exception_warning. * Remove incorrect and misplaced comments. * Update translator comments. * Update API reference to document all missing and incomplete documentation.
Diffstat (limited to 'README')
-rw-r--r--README13
1 files changed, 7 insertions, 6 deletions
diff --git a/README b/README
index 71fcb32b..fcf4a278 100644
--- a/README
+++ b/README
@@ -3,12 +3,13 @@ schroot
Securely enter a chroot and run a command or login shell.
-Note that giving untrusted users root access to chroots is a bad idea.
-Although they will only have root access to files inside the chroot,
-in practice there are many obvious ways of breaking out of the chroot
-or disrupting services on the host system. As always, this boils down
-to trust. Don't give root access to chroots to users you would not
-trust with root access to the host system.
+Note that giving untrusted users root access to chroots is a serious
+security risk!. Although the untrusted user will only have root
+access to files inside the chroot, in practice there are many obvious
+ways of breaking out of the chroot and of disrupting services on the
+host system. As always, this boils down to trust. Don't give chroot
+root access to users you would not trust with root access to the host
+system.
For compatibility with existing tools and scripts, wrapper binaries
for dchroot and DSA dchroot are provided.