Why do I need anonymous login for ProFTPD server?

Why do I need anonymous login for ProFTPD server?

Anonymous logins are used to allow users with no accounts on server to access specific directory in system hierarchy, which by default in CentOS / RHEL 7 is /var/ftp directory, without the need for the anonymous user to enter a password.

Is the ProFTPD file the same as the system?

proftpd uses your system’s /etc/passwd file by default, and so proftpd users are the same as your system users. “Virtual” users, sometimes described as FTP-only user accounts, are users that can login to proftpd , but who are separate from the normal system users, and who do not have entries in /etc/passwd .

Is there a way to disable Pam in ProFTPD?

If it does, the mod_auth_pammodule will automatically be compiled into your proftpd. If you explicitly do not want PAM support, you can use the –disable-auth-pamconfigure option to disable this automatic detection. The point of using PAM is that it can provide an extra authentication step during a login.

What are the two authentication modules in ProFTPD?

The default build of proftpd has two authentication modules included: mod_auth_file and mod_auth_unix . proftpd will consult both modules when authenticating a user: first mod_auth_file, then mod_auth_unix . ( Note: versions of proftpd before 1.2.8rc1 would only support either AuthUserFile or /etc/passwd,…

Which is the default FTP directory for anonymous users?

The default served FTP Anonymous directory is /var/ftp/ system path, which contains two directories with different permissions. pub directory – The public FTP directory which can be read and listed by all anonymously authenticated users. Here you can put files for clients to access and download.

Where is the anonymous block directive stored in ProFTPD?

While the anonymous block directive usually is stored in the main Proftpd configuration file.

How to force anonymous logins to be bound to another user?

To force anonymous logins to be bound to a user other than the current user, see the User and Group directives. In addition, if a User or Group directive is present in an block, the daemon permanently switches to the specified uid/gid before chroot()ing.