im pretty new to the world of linux, server management and ssh so you might have to bare with me here

so basically i want to be able to give my ftp users access to multiple directories.

i have my vsftp setup to use virtual users and each user has (or can have) individual config files.

the main problem i am having is that the server has a number of virtual hosts setup on it and i want to give access to some of those directories only to some users and all to other users. For example

User1 -/var/www/vhost/domain1.com -/var/www/vhost/domain2.com -/var/www/vhost/domain3.com -/var/www/vhost/domain4.com

User2 -/var/www/vhost/domain1.com -/var/www/vhost/domain4.com

User3 -/var/www/vhost/domain2.com

Because of the crossover i cant just put the virtual hosts into seperate home folders. I have also tried creating symlinks to the virtual host directories into the seperate users home directories but because the users are locked to their home directories you cant follow them

here is a copy of my vsftpd.config file (local server but same setup)

# Example config file /etc/vsftpd/vsftpd.conf
# The default compiled in settings are fairly paranoid. This sample file
# loosens things up a bit, to make the ftp daemon more usable.
# Please see vsftpd.conf.5 for all compiled in defaults.
# READ THIS: This example file is NOT an exhaustive list of vsftpd options.
# Please read the vsftpd.conf.5 manual page to get a full idea of vsftpd's
# capabilities.
# Allow anonymous FTP? (Beware - allowed by default if you comment this out).
# Uncomment this to allow local users to log in.
# Uncomment this to enable any form of FTP write command.
# Default umask for local users is 077. You may wish to change this to 022,
# if your users expect that (022 is used by most other ftpd's)
# Uncomment this to allow the anonymous FTP user to upload files. This only
# has an effect if the above global write enable is activated. Also, you will
# obviously need to create a directory writable by the FTP user.
# Uncomment this if you want the anonymous FTP user to be able to create
# new directories.
# Activate directory messages - messages given to remote users when they
# go into a certain directory.
# The target log file can be vsftpd_log_file or xferlog_file.
# This depends on setting xferlog_std_format parameter
# Make sure PORT transfer connections originate from port 20 (ftp-data).
# If you want, you can arrange for uploaded anonymous files to be owned by
# a different user. Note! Using "root" for uploaded files is not
# recommended!
# The name of log file when xferlog_enable=YES and xferlog_std_format=YES
# WARNING - changing this filename affects /etc/logrotate.d/vsftpd.log
# Switches between logging into vsftpd_log_file and xferlog_file files.
# NO writes to vsftpd_log_file, YES to xferlog_file
# You may change the default value for timing out an idle session.
# You may change the default value for timing out a data connection.
# It is recommended that you define on your system a unique user which the
# ftp server can use as a totally isolated and unprivileged user.
# Enable this and the server will recognise asynchronous ABOR requests. Not
# recommended for security (the code is non-trivial). Not enabling it,
# however, may confuse older FTP clients.
# By default the server will pretend to allow ASCII mode but in fact ignore
# the request. Turn on the below options to have the server actually do ASCII
# mangling on files when in ASCII mode.
# Beware that on some FTP servers, ASCII support allows a denial of service
# attack (DoS) via the command "SIZE /big/file" in ASCII mode. vsftpd
# predicted this attack and has always been safe, reporting the size of the
# raw file.
# ASCII mangling is a horrible feature of the protocol.
# You may fully customise the login banner string:
#ftpd_banner=Welcome to blah FTP service.
# You may specify a file of disallowed anonymous e-mail addresses. Apparently
# useful for combatting certain DoS attacks.
# (default follows)
# You may specify an explicit list of local users to chroot() to their home
# directory. If chroot_local_user is YES, then this list becomes a list of
# users to NOT chroot().
# (default follows)
# You may activate the "-R" option to the builtin ls. This is disabled by
# default to avoid remote users being able to cause excessive I/O on large
# sites. However, some broken FTP clients such as "ncftp" and "mirror" assume
# the presence of the "-R" option, so there is a strong case for enabling it.
# When "listen" directive is enabled, vsftpd runs in standalone mode and
# listens on IPv4 sockets. This directive cannot be used in conjunction
# with the listen_ipv6 directive.
# This directive enables listening on IPv6 sockets. To listen on IPv4 and IPv6
# sockets, you must run two copies of vsftpd with two configuration files.
# Make sure, that one of the listen options is commented !!






i hope this includes everything you need, as i say im a novice at this point

any help would be appreciated


i stumbles across a solution to this problem this morning and as in my searches i found several people asking the same question that had not found a god solution i thought is add it here for googlers.

(if anyone knows of a better solution please let me know)

The solution i found HERE is to mount the directories of the virtual hosts in each users respective home directories, this allows the directories to be accessed as if they were actual sub directories of said users home

to mount a directory temporally

mkdir /home/ftp_user/www_dev #create directory to mount too
mount --bind /var/www/dev/ /home/ftp_user/www_dev #mount the directory

if you wish to have this setup perminentry create the directory to mount to and then add a line to /etc/fstab

/var/www/dev  /home/ftp_user/www_dev    none    bind    0       0

hope this helps someone

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.