Hi, ive created user in my server for vsftp and they are chroot when they use the ftp but not when they use the shell.How to chroot them into the shell please?Thank you [by KDFKDF]
on 07/31/2009 – Made popular on 07/31/2009
Hi. I have a question about chroot and su from within chroot! How is it that Midnight Commander running inside of my chroot discovers the name of my non-chroot user account and also ignores the chroot user account? This leads to the following error message: "Cannot create /home/dano/.config/mc directory" which shows that M.C.
Kilzool wrote:You could write your own SHELL, and chroot them into it.As much as I would like to write my own SHELL, and chroot them into it, I'm not an advanced enough user to do something like that. Maybe someday, but not at the moment.
In my Android-hosted Ubuntu 13.04 chroot, I am attempting to get gnome-shell running on Xvfb. I've handled rendering issues as far as I know, and now I'm having trouble with gnome-shell. I suspect D-Bus.
I've gotten D-Bus running in my chroot by using this special python-based replacement of upstart and running /etc/init.d/rcS, /etc/init.d/rc 2 and start upstart. X starts up swimmingly.
falconindy wrote:tychicus wrote:However, the mount point is still listed in /proc/mounts in the chroot environment!Not relevant -- /proc/mounts doesn't respect namespaces and subroots. Use /proc/self/mountinfo (from the chrooted shell) if you want an accurate portrayal of what's mounted in the chroot.Okay that makes sense then.
I've been playing around with CentOS box for couple of years now. So I'm pretty comfy with terminal. However, I read a lot of blog-post claiming that chroot is insecure and amount of those posts frightens. Is it really so? Why?
I use chroot to lockdown the SFTP-only users in specific context, without any shell or commands at all.