Dedicated server and vsftpd. I need help with that. PLEASE.
#1

Hi, guys. I have dedicated server and i wanna make my company for samp servers. So i installed vsftpd on my dedicated server and i created a few users with FTP. Now everyone has a access to all my files on dedicated server. Can someone tell me how to limit users to only their home directory I need it so bad. Thank you!

P.S IF somebody help me out with that. I will give you SA-MP server for FREE!
Reply
#2

Pal try installing a CPanel type software and use that for the VPS's/SA-MP Servers ect.

You can find many guides online for shit like this.
Reply
#3

Spydro, Hi. I already have GameCP and I already tried all guides online and it's still doesn't work for me -_-
Reply
#4

forgot to chroot the users?
Reply
#5

Sublime, # Allow anonymous FTP? (Beware - allowed by default if you comment this out).
anonymous_enable=NO
#
# Uncomment this to allow local users to log in.
local_enable=YES
#
# Uncomment this to enable any form of FTP write command.
write_enable=YES
#
# 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)
local_umask=022
#
# 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.
#anon_upload_enable=YES
#
# Uncomment this if you want the anonymous FTP user to be able to create
# new directories.
#anon_mkdir_write_enable=YES
#
# Activate directory messages - messages given to remote users when they
# go into a certain directory.
dirmessage_enable=YES
#
# The target log file can be vsftpd_log_file or xferlog_file.
# This depends on setting xferlog_std_format parameter
xferlog_enable=YES
#
# Make sure PORT transfer connections originate from port 20 (ftp-data).
connect_from_port_20=YES
#
# 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!
#chown_uploads=YES
#chown_username=whoever
#
# The name of log file when xferlog_enable=YES and xferlog_std_format=YES
# WARNING - changing this filename affects /etc/logrotate.d/vsftpd.log
#xferlog_file=/var/log/xferlog
#
# Switches between logging into vsftpd_log_file and xferlog_file files.
# NO writes to vsftpd_log_file, YES to xferlog_file
xferlog_std_format=YES
#
# You may change the default value for timing out an idle session.
#idle_session_timeout=600
#
# You may change the default value for timing out a data connection.
#data_connection_timeout=120
#
# 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.
#nopriv_user=ftpsecure
#
# 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.
#async_abor_enable=YES
#
# 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.
#ascii_upload_enable=YES
#ascii_download_enable=YES
#
# 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.
#deny_email_enable=YES
# (default follows)
#banned_email_file=/etc/vsftpd/banned_emails
#
# 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().
#chroot_local_user=YES
#chroot_list_enable=YES
# (default follows)
#chroot_list_file=/etc/vsftpd/chroot_list
#
# 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.
#ls_recurse_enable=YES
#
# 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.
listen=YES
#
# 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 !!
#listen_ipv6=YES

pam_service_name=vsftpd
userlist_enable=YES
tcp_wrappers=YES
Reply
#6

set chroot_local_user to yes then execute usermod on whatever user you want to restrict access to

usermod --home /enter/your/directory/here/ ftp_username
Reply
#7

Are you sure that you can handle all the technical challenges that hosting brings, if you cant even handle something as simple as file permissions and ftp chroot?
Reply
#8

I use
pawn Код:
chroot_local_user=YES
Then you will need to set user's home dir, and remove write flag from that dir (or you wont be able to connect to FTP with that user).

If you want to allow your users to write in home dir
pawn Код:
allow_writeable_chroot=YES
Please note that conf. variable is for vsftpd 3.0+ (I think 14.04 uses 3.x)
If you are on 12.04 then read third post from http://askubuntu.com/questions/12818...g-after-update

That will install vsftpd from unofficial repository so keep that in mind.
Reply
#9

if it's not supported by the distribution's official repository, then it is not meant as a stable release for said distribution version
Reply
#10

Quote:
Originally Posted by Sublime
Посмотреть сообщение
if it's not supported by the distribution's official repository, then it is not meant as a stable release for said distribution version
I get what you are saying but i have been using it for a long time and i can tell you its stable. In any case using unofficial repositories means if something goes south you can blame only yourself (that is what you are saying ). But in some cases using unofficial repositories is better than using official...For example node.js package from ubuntu official repository on 14.04 just breaks half the things only because some idiot decided to rename freaking directory...
Reply


Forum Jump:


Users browsing this thread: 2 Guest(s)