Linux – Can a user be excluded from /etc/profile.d scripts

Must have to do with diff between su-ing over ssh vs when logged directly into machine

I suspect that you execute the su command without dash (-), and if so, it will invoke an interactive non-login shell. Combine with you have only following in /root/.bashrc:

# Test for an interactive shell.  There is no need to set anything
# past this point for scp and rcp, and it's important to refrain from
# outputting anything in those cases.
if [[ $- != *i* ]] ; then
    # Shell is non-interactive.  Be done now!
    return
fi

(not source /etc/bashrc)

whereas if you directly login or use su -, it will invoke a login shell, /etc/profile is read and sharedAliases.sh will be execute.

To see which file is read with different shells, adding logs to all these files by executing the following commands as root:

echo "echo 'running /etc/bashrc'" >> /etc/bashrc
echo "echo 'running /etc/profile'" >> /etc/profile
echo "echo 'running /root/.bashrc'" >> ~/.bashrc

Create an test alias:

# echo "alias list='ls'" > /etc/profile.d/test.sh

Now, login as normal user and use su, you will see something like this:

$ su
Password: 
running /root/.bashrc
bash-3.2# list
bash: list: command not found

and with su -:

$ su -
Password: 
running /etc/profile
running /root/.bashrc
# list
total 226540
-rw-rw-r-- 1 root root     60148987 Apr  1  2011 3241948.flv

Your configuration is correct except for a small detail: the home directory in /etc/passwd should not contain the chroot path part. Change it to:

test:x:1004:1008:,,,:/home/test:/bin/bash

restart sshd and try again.

From man sshd_config:

ChrootDirectory

Specifies the pathname of a directory to chroot(2) to after authentication. All components of the pathname must be root-owned directories that are not writable by any other user or group. After the chroot, sshd(8) changes the working directory to the user's home directory.

That is, first sshd executes chroot (in our case chroot /var/jail), and then sshd changes the directory to the user's homedir (in our case cd /home/test - in a chrooted environment cd /var/jail/home/test wouldn't work).

If you are using Debian/Ubuntu (since the tutorial you mention is for Debian) you may want to create a file named /var/jail/etc/debian_chroot with contents "chroot", this will appear in the user prompt in parentheses like this: (chroot)test@servername:~$.

(I've duplicated your configuration on my Ubuntu 12.04 and it has worked after removing /var/jail from user test's entry in /etc/passwd.)