Originally Posted by till
Only new users are chrooted or users that have been edited. You must also make sute that you really enabled chrooting in the config.inc.php file.
$go_info["server"]["ssh_chroot"] = 1;
As posted, a typical new or edited user looks like:
Yet, when this users attempts to log in, he is punted with a:
/bin/bash: No such file or directory
hyperion:/home/chroot/bin# ls -al
drwxr-sr-x 2 root staff 4096 Mar 9 10:11 .
drwxr-sr-x 8 root staff 4096 Mar 9 10:10 ..
-rwxr-xr-x 1 root staff 625228 Mar 9 10:11 bash
-rwxr-xr-x 1 root staff 75948 Mar 9 10:11 ls
-rwxr-xr-x 1 root staff 20888 Mar 9 10:11 mkdir
-rwxr-xr-x 1 root staff 55340 Mar 9 10:11 mv
-rwsr-xr-x 1 root staff 30764 Mar 9 10:11 ping
-rwxr-xr-x 1 root staff 13848 Mar 9 10:11 pwd
-rwxr-xr-x 1 root staff 30712 Mar 9 10:11 rm
Each chrooted user's home directory contains the same files as listed above. That all looks right, but the user cannot find bash when he logs in.
I am kind of confused about the use of the chrooted /etc/passwd and group files. ISPConfig doesn't update them when I create or edit new users, rather it updates the system proper /etc/passwd and group files. Is that correct behaviour?