Causes: In recent fiddle Linux, configure vsftp when problems are discovered permission pit, headache one day and found a little problem
Common authentication method:
1. User Authentication System
For example vsftp this software if you want to build a user can log on FTP, we recommend that the user can not give permission to log on the system shell
useradd -s /sbin/nologin xxx
Use of the code we can specify that the user is not logged rights system shell but he can serve as a user login FTP, the default directory of the FTP server is really under their own home directory of the user logs on to the case, that if we want to assign to the user he logs fixed to the directory where the FTP service, then we can join in the new -d parameter specifies the user when the user's home directory can be achieved
2. Use the software authentication mechanism itself
Such software such as samba, although he also needs to create a user in a Linux system but the real authentication service is provided by samba itself, we only need to create a user account and then use the smbpasswd -a to create a new password on the system
3. Use a credible third-party organizations
Kerberos authentication server such as this can also provide authentication
Then I met said pit
Put brother's profile
# 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). anonymous_enable=NO allow_writeable_chroot=YES # Uncomment this to allow local users to log in. # When SELinux is enforcing check for SE bool ftp_home_dir 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. # When SELinux is enforcing check for SE bool allow_ftpd_anon_write, allow_ftpd_full_access 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 # # 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/xferlog # # 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. The vsftpd.conf(5) man page explains # the behaviour when these options are disabled. # 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(). # (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 local_root=/var/ftp #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=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. # Make sure, that one of the listen options is commented !! listen_ipv6=YES pam_service_name=vsftpd userlist_enable=NO tcp_wrappers=YES
The owner and group folders on
It measured two Linux systems, Ubuntu16.04 and redhat7.6
Ubuntu users and groups in which success is created by default after installation vsftp are ftp
The default Redhat create users and groups are vsftp
Ubuntu
Redhat
I always felt not as easy to put selinux off, so tested, only open bool value ftpd_full_access is on when you can achieve normal ftp function, if you want to allow any user to upload files, then need to open ftpd_anon_write, if you want to use FTP passive mode requires open ftpd_use_passive_mode
Open statement can refer to
setsebool ftpd_full_access -P 1
Similarly we have to release the FTP service on the firewall
Command Reference
firewall-cmd --add-service=ftp firewall-cmd --add-service=ftp --permanent firewall-cmd --reload
The first temporary release as FTP service, the failure after the restart, the second is written into the underlayer, to take effect after the restart but any course may be restarted before the entry into force, so that with the use of twelve, or may be performed to achieve the same twenty-three Effect
Then is the file directory on the folder permission settings, the authority recommended on Redhat / var / ftp directory is set to 755, the owner and group set to vsftp
Local users to upload files permission is generally 644, 755 is generally folder, this is because the default configuration file permissions mask umask = 022 role
Being on these bigwigs a lot of corrections
