https://bugs.koozali.org/show_bug.cgi?id=3178

--- Comment #28 from Jean-Philippe Pialasse <[email protected]> ---
checking more on that:

so there are two way to chroot using ssh

1# rssh  with default /home/e-smith/files/users/user/home chroot
needs to update the /etc/e-smith/templates/etc/rssh.conf/40users from
e-smith-openssh
to add the path to chroot
also need to have the user with shell access and finally set RSSH to yes


however it fails by closing  immediatly the sftp user@server
because it needs a full real chroot with needed devices, lib and bins
https://www.cyberciti.biz/tips/howto-linux-unix-rssh-chroot-jail-setup.html


2# internal sftp with default /home/e-smith/files/users/user/home chroot

this require the whole subdirs of the chroot dir to be root owned
examples of failure

fatal: bad ownership or modes for chroot directory component "/home/e-smith/"
[postauth]

ok then doing
chown root:root /home/e-smith/

fatal: bad ownership or modes for chroot directory component
"/home/e-smith/files/users/user/" [postauth]

bumer 

"All components of the pathname must be root-owned directories that are not
writable by any other user or group"

however if you set to /home/e-smith/files/ibays/Primary all is ok 

so back to square one and bug 12213 with a real jail chroot on the side with
mount bind

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
You are the assignee for the bug.
_______________________________________________
Mail for each SME Contribs bug report
To unsubscribe, e-mail [email protected]
Searchable archive at https://lists.contribs.org/mailman/public/contribteam/

Reply via email to