Score:0

VSFTPD Access error

dk flag

I have a problem. I configured my vsftpd for two users, using the commands (without forgetting about the configuration file).:

riven@riven:~$ sudo adduser r1ven riven@riven:~$ sudo adduser max    riven@riven:~$ sudo addgroup adm1n riven@riven:~$ sudo chgrp -R adm1n    /home/riven/Desktop/ExLand 
riven@riven:~$ sudo chmod -R 770 /home/riven/Desktop/ExLand 
riven@riven:~$ sudo usermod -a -G adm1n  r1ven
riven@riven:~$ sudo usermod -a -G adm1n max
riven@riven:~$ sudo mkdir /home/r1ven/ExLand
riven@riven:~$ sudo mkdir /home/max/ExLand
riven@riven:~$ sudo chown nobody:nogroup/home/r1ven/ExLand
riven@riven:~$ sudo chown nobody:nogroup/home/max/ExLand
riven@riven:~$ sudo chmod a-w /home/r1ven/ExLand
riven@riven:~$ sudo chmod a-w /home/max/ExLand
riven@riven:~$ sudo ln -s /home/riven/Desktop/ExLand /home/r1ven/ExLand
riven@riven:~$ sudo ln -s /home/riven/Desktop/ExLand /home/max/ExLand

My vsftpd config file:

# Example config file /etc/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.
#
#
# Run standalone?  vsftpd can run either from an inetd or as a standalone
# daemon started from an initscript.
listen=NO
#
# This directive enables listening on IPv6 sockets. By default, listening
# on the IPv6 "any" address (::) will accept connections from both IPv6
# and IPv4 clients. It is not necessary to listen on *both* IPv4 and IPv6
# sockets. If you want that (perhaps because you want to listen on specific
# addresses) then you must run two copies of vsftpd with two configuration
# files.
listen_ipv6=YES
#
# Allow anonymous FTP? (Disabled by default).
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
#
user_sub_token=$USER
#
local_root=/home/$USER/ExLand
#
chroot_local_user=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
#
# If enabled, vsftpd will display directory listings with the time
# in  your  local  time  zone.  The default is to display GMT. The
# times returned by the MDTM FTP command are also affected by this
# option.
use_localtime=YES
#
# Activate logging of uploads/downloads.
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
#
# You may override where the log file goes if you like. The default is shown
# below.
#xferlog_file=/var/log/vsftpd.log
#
# If you want, you can have your log file in standard ftpd xferlog format.
# Note that the default log file location is /var/log/xferlog in this case.
#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 restrict local users to their home directories.  See the FAQ for
# the possible risks in this before using chroot_local_user or
# chroot_list_enable below.
#chroot_local_user=YES
#
# 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().
# (Warning! chroot'ing can be very dangerous. If using chroot, make sure that
# the user does not have write access to the top level directory within the
# 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
#
# Customization
#
# Some of vsftpd's settings don't fit the filesystem layout by
# default.
#
# This option should be the name of a directory which is empty.  Also, the
# directory should not be writable by the ftp user. This directory is used
# as a secure chroot() jail at times vsftpd does not require filesystem
# access.
secure_chroot_dir=/var/run/vsftpd/empty
#
# This string is the name of the PAM service vsftpd will use.
pam_service_name=vsftpd
#
force_dot_files=YES
pasv_min_port=40000
pasv_max_port=50000
# This option specifies the location of the RSA certificate to use for SSL
# encrypted connections.
rsa_cert_file=/etc/ssl/certs/ssl-cert-snakeoil.pem
rsa_private_key_file=/etc/ssl/private/ssl-cert-snakeoil.key
ssl_enable=NO

But when I try to connect via filezilla to my server, an access error occurs when I click on the "Exland" shortcut. (Screenshot below) I don't even know what to do. Please help a beginner in the world of ubuntu)

enter image description here

Access rules in folders: Exland folder (in home/riven/Desktop) - enter image description here r1ven folder (in /home/) - enter image description here Exland folder (in home/r1ven/) - enter image description here Exland Link to folder (in /home/r1ven/Exland/) - enter image description here

in flag
Welcome to AskUbuntu. Do both of the users have `ExLand` in their home directory? If they do, have you confirmed that the proper permissions are set?
Riven avatar
dk flag
matigo, The commands reflect that I created the adm1n group and assigned the users r1ven and max to it and gave the group access to the Exland directory
in flag
Indeed. The commands are listed, but not the response. Hence my question. I really, *really* dislike investing 20+ minutes in writing a possible answer only to discover that something basic wasn't confirmed ahead of time
Riven avatar
dk flag
matigo, What responses do you need? responses to these commands in ubuntu shell? Or maybe some logs? I am just a new user in ubuntu.
Riven avatar
dk flag
matigo, i add screens (access rules in folders (by GUI))
I sit in a Tesla and translated this thread with Ai:

mangohost

Post an answer

Most people don’t grasp that asking a lot of questions unlocks learning and improves interpersonal bonding. In Alison’s studies, for example, though people could accurately recall how many questions had been asked in their conversations, they didn’t intuit the link between questions and liking. Across four studies, in which participants were engaged in conversations themselves or read transcripts of others’ conversations, people tended not to realize that question asking would influence—or had influenced—the level of amity between the conversationalists.