Find the answer to your Linux question:
Page 3 of 3 FirstFirst 1 2 3
Results 21 to 22 of 22
Well, that's most likely the problem. The home directory to which you chroot the user MUST be owned by root with permissions of 755. I'm pretty sure the same rules ...
Enjoy an ad free experience by logging in. Not a member yet? Register.
  1. #21
    Just Joined!
    Join Date
    Jul 2011
    Location
    Cincinnati, OH
    Posts
    6

    Well, that's most likely the problem. The home directory to which you chroot the user MUST be owned by root with permissions of 755. I'm pretty sure the same rules apply to any directories above that one. Therefore, I would not be using /tmp as your test as you need to take away write permissions for everyone except for root for the chroot directory and every directory above it all the way up to root. Other users or programs may be writing to /tmp. I would recommend creating a /chroot directory, then another directory below that with the same permissions, modifying your /etc/ssh/sshd_config file with those changes, restart the sshd process and try it again.

  2. #22
    Just Joined!
    Join Date
    Jun 2012
    Posts
    1
    Here's what worked for me, in case someone else is having issues with this.

    There are multiple scenarios:

    1.

    chroot_local_user=YES
    chroot_list_enable=YES
    chroot_list_file=/etc/vsftpd/chroot_list

    If you keep the chroot_list empty then the configuration will work.

    BUT if you start adding users in chroot_list, then it will have the opposite effect, those users are users that are not jailed.

    2.

    chroot_local_user=NO
    chroot_list_enable=YES
    chroot_list_file=/etc/vsftpd/chroot_list

    With this config you can add users in chroot_list, which will contain a list with users that are jailed to their home directories.

Page 3 of 3 FirstFirst 1 2 3

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •