Alright. I've been trying to figure out this mystery for a long LONG time now. For a while I had a server running vsftpd with chroot and it worked just fine, but I had to reinstall the OS and wipe everything out. Ever since the new install chroot has never worked.
Now, I don't know much about chroot outside of how it should be used in vsftpd to jail users, but I assume this command should at least work:
Code:
[root@kitsapbands etc]# chroot /etc/
chroot: /bin/bash: No such file or directory
[root@kitsapbands etc]# chroot ../etc/
chroot: /bin/bash: No such file or directory
My vsftpd.conf is as follows:
Code:
anonymous_enable=NO
local_enable=YES
write_enable=YES
local_umask=022
anon_upload_enable=NO
anon_mkdir_write_enable=NO
dirmessage_enable=YES
xferlog_enable=YES
connect_from_port_20=YES
#chown_uploads=YES
#chown_username=whoever
xferlog_std_format=YES
chroot_list_enable=NO
chroot_local_user=YES
chroot_list_file=/etc/vsftpd.chroot_list
#ls_recurse_enable=YES
pam_service_name=vsftpd
userlist_enable=YES
#enable for standalone mode
#listen=YES
#tcp_wrappers=YES
The vsftpd.chroot_list has 3 accounts in it, and I've tried alternating the use of chroot_local_user and chroot_list_file to see if vsftpd would either jail the people in the list or the people not in the list, but no luck.
To start vsftpd I just run:
Code:
service vsftpd start
Is this the right way it should be done?
Something here just isn't working. Is chroot not working right, or is it vsftpd?