Différences
Ci-dessous, les différences entre deux révisions de la page.
Les deux révisions précédentesRévision précédenteProchaine révision | Révision précédente | ||
logiciel:internet:ftp:vsftpd:config:man:start [2020/12/22 15:09] – [Options booléennes] admin | logiciel:internet:ftp:vsftpd:config:man:start [2022/08/13 22:36] (Version actuelle) – modification externe 127.0.0.1 | ||
---|---|---|---|
Ligne 3: | Ligne 3: | ||
====== Page de man vsftpd.conf ====== | ====== Page de man vsftpd.conf ====== | ||
- | ====== Nom ====== | + | ===== Nom ===== |
- | | + | |
: fichier de configuration pour vsftpd | : fichier de configuration pour vsftpd | ||
- | ====== Description | + | ===== Description ===== |
Le fichier / | Le fichier / | ||
- | ====== Format | + | ===== Format ===== |
Le format de vsftpd.conf est très simple. Chaque ligne est un commentaire ou une directive. | Le format de vsftpd.conf est très simple. Chaque ligne est un commentaire ou une directive. | ||
Ligne 24: | Ligne 24: | ||
Chaque paramètre a une valeur par défaut modifiable dans le fichier de configuration. | Chaque paramètre a une valeur par défaut modifiable dans le fichier de configuration. | ||
- | ====== Options booléennes | + | ===== Options booléennes ===== |
Below is a list of boolean options. The value for a boolean option may be set to YES or NO. | Below is a list of boolean options. The value for a boolean option may be set to YES or NO. | ||
- | | + | |
: Only applies if ssl_enable is active. | : Only applies if ssl_enable is active. | ||
: If set to YES, anonymous users will be allowed to use secured SSL connections. | : If set to YES, anonymous users will be allowed to use secured SSL connections. | ||
: Default: **NO** | : Default: **NO** | ||
- | | + | |
: \\ If set to YES, anonymous users will be permitted to create new directories under certain conditions. | : \\ If set to YES, anonymous users will be permitted to create new directories under certain conditions. | ||
: For this to work, the option write_enable must be activated, and the anonymous ftp user must have write permission on the parent directory. | : For this to work, the option write_enable must be activated, and the anonymous ftp user must have write permission on the parent directory. | ||
: Default: **NO** | : Default: **NO** | ||
- | | + | |
: \\ If set to YES, anonymous users will be permitted to perform write operations other than upload and create directory, such as deletion and renaming. | : \\ If set to YES, anonymous users will be permitted to perform write operations other than upload and create directory, such as deletion and renaming. | ||
: This is generally not recommended but included for completeness. | : This is generally not recommended but included for completeness. | ||
: Default: NO | : Default: NO | ||
- | | + | |
: \\ If set to YES, anonymous users will be permitted to upload files under certain conditions. | : \\ If set to YES, anonymous users will be permitted to upload files under certain conditions. | ||
: For this to work, the option write_enable must be activated, and the anonymous ftp user must have write permission on desired upload locations. | : For this to work, the option write_enable must be activated, and the anonymous ftp user must have write permission on desired upload locations. | ||
: This setting is also required for virtual users to upload; by default, virtual users are treated with anonymous (i.e. maximally restricted) privilege. | : This setting is also required for virtual users to upload; by default, virtual users are treated with anonymous (i.e. maximally restricted) privilege. | ||
: Default: **NO** | : Default: **NO** | ||
- | | + | |
: \\ When enabled, anonymous users will only be allowed to download files which are world readable. | : \\ When enabled, anonymous users will only be allowed to download files which are world readable. | ||
: This is recognising that the ftp user may own files, especially in the presence of uploads. | : This is recognising that the ftp user may own files, especially in the presence of uploads. | ||
: Default: **YES** | : Default: **YES** | ||
- | | + | |
: Controls whether anonymous logins are permitted or not. | : Controls whether anonymous logins are permitted or not. | ||
: If enabled, both the usernames ftp and anonymous are recognised as anonymous logins. | : If enabled, both the usernames ftp and anonymous are recognised as anonymous logins. | ||
: Default: **YES** | : Default: **YES** | ||
- | | + | |
: \\ When enabled, ASCII mode data transfers will be honoured on downloads. | : \\ When enabled, ASCII mode data transfers will be honoured on downloads. | ||
: Default: **NO** | : Default: **NO** | ||
- | | + | |
: \\ When enabled, ASCII mode data transfers will be honoured on uploads. | : \\ When enabled, ASCII mode data transfers will be honoured on uploads. | ||
: Default: **NO** | : Default: **NO** | ||
- | | + | |
: \\ When enabled, a special FTP command known as "async ABOR" will be enabled. | : \\ When enabled, a special FTP command known as "async ABOR" will be enabled. | ||
: Only ill advised FTP clients will use this feature. | : Only ill advised FTP clients will use this feature. | ||
Ligne 65: | Ligne 65: | ||
: Unfortunately, | : Unfortunately, | ||
: Default: **NO** | : Default: **NO** | ||
- | | + | |
: \\ When enabled, and vsftpd is started in " | : \\ When enabled, and vsftpd is started in " | ||
: Default: **NO** | : Default: **NO** | ||
- | | + | |
: Note! This option only has an effect for non-PAM builds of vsftpd. | : Note! This option only has an effect for non-PAM builds of vsftpd. | ||
: If disabled, vsftpd will not check /etc/shells for a valid user shell for local logins. | : If disabled, vsftpd will not check /etc/shells for a valid user shell for local logins. | ||
: Default: **YES** | : Default: **YES** | ||
- | | + | |
: \\ When enabled, allows use of the SITE CHMOD command. | : \\ When enabled, allows use of the SITE CHMOD command. | ||
: NOTE! This only applies to local users. | : NOTE! This only applies to local users. | ||
: Anonymous users never get to use SITE CHMOD. | : Anonymous users never get to use SITE CHMOD. | ||
: Default: **YES** | : Default: **YES** | ||
- | | + | |
: \\ If enabled, all anonymously uploaded files will have the ownership changed to the user specified in the setting chown_username. | : \\ If enabled, all anonymously uploaded files will have the ownership changed to the user specified in the setting chown_username. | ||
: This is useful from an administrative, | : This is useful from an administrative, | ||
: Default: **NO** | : Default: **NO** | ||
- | | + | |
: \\ If activated, you may provide a list of local users who are placed in a chroot() jail in their home directory upon login. | : \\ If activated, you may provide a list of local users who are placed in a chroot() jail in their home directory upon login. | ||
: The meaning is slightly different if chroot_local_user is set to YES. | : The meaning is slightly different if chroot_local_user is set to YES. | ||
Ligne 87: | Ligne 87: | ||
: By default, the file containing this list is / | : By default, the file containing this list is / | ||
: Default: **NO** | : Default: **NO** | ||
- | | + | |
: \\ If set to YES, local users will be (by default) placed in a chroot() jail in their home directory after login. | : \\ If set to YES, local users will be (by default) placed in a chroot() jail in their home directory after login. | ||
: Warning: This option has security implications, | : Warning: This option has security implications, | ||
Ligne 94: | Ligne 94: | ||
: They apply to all FTP daemons which offer to put local users in chroot() jails. | : They apply to all FTP daemons which offer to put local users in chroot() jails. | ||
: Default: **NO** | : Default: **NO** | ||
- | | + | |
: This controls whether PORT style data connections use port 20 (ftp-data) on the server machine. | : This controls whether PORT style data connections use port 20 (ftp-data) on the server machine. | ||
: For security reasons, some clients may insist that this is the case. | : For security reasons, some clients may insist that this is the case. | ||
: Conversely, disabling this option enables vsftpd to run with slightly less privilege. | : Conversely, disabling this option enables vsftpd to run with slightly less privilege. | ||
: Default: **NO (but the sample config file enables it)** | : Default: **NO (but the sample config file enables it)** | ||
- | | + | |
: \\ If true, OpenSSL connection diagnostics are dumped to the vsftpd log file. (Added in v2.0.6). | : \\ If true, OpenSSL connection diagnostics are dumped to the vsftpd log file. (Added in v2.0.6). | ||
: Default: **NO** | : Default: **NO** | ||
- | | + | |
: \\ If true, any failed upload files are deleted. (Added in v2.0.7). | : \\ If true, any failed upload files are deleted. (Added in v2.0.7). | ||
: Default: **NO** | : Default: **NO** | ||
- | | + | |
: \\ If activated, you may provide a list of anonymous password e-mail responses which cause login to be denied. | : \\ If activated, you may provide a list of anonymous password e-mail responses which cause login to be denied. | ||
: By default, the file containing this list is / | : By default, the file containing this list is / | ||
: Default: **NO** | : Default: **NO** | ||
- | | + | |
: \\ If set to NO, all directory list commands will give permission denied. | : \\ If set to NO, all directory list commands will give permission denied. | ||
: Default: **YES** | : Default: **YES** | ||
- | | + | |
: \\ If enabled, users of the FTP server can be shown messages when they first enter a new directory. | : \\ If enabled, users of the FTP server can be shown messages when they first enter a new directory. | ||
: By default, a directory is scanned for the file .message, but that may be overridden with the configuration setting message_file. | : By default, a directory is scanned for the file .message, but that may be overridden with the configuration setting message_file. | ||
: Default: **NO (but the sample config file enables it)** | : Default: **NO (but the sample config file enables it)** | ||
- | | + | |
: \\ If set to NO, all download requests will give permission denied. | : \\ If set to NO, all download requests will give permission denied. | ||
: Default: **YES** | : Default: **YES** | ||
- | | + | |
: \\ If enabled, two log files are generated in parallel, going by default to / | : \\ If enabled, two log files are generated in parallel, going by default to / | ||
: The former is a wu-ftpd style transfer log, parseable by standard tools. | : The former is a wu-ftpd style transfer log, parseable by standard tools. | ||
: The latter is vsftpd' | : The latter is vsftpd' | ||
: Default: **NO** | : Default: **NO** | ||
- | | + | |
: \\ If activated, files and directories starting with . will be shown in directory listings even if the " | : \\ If activated, files and directories starting with . will be shown in directory listings even if the " | ||
: This override excludes the " | : This override excludes the " | ||
: Default: **NO** | : Default: **NO** | ||
- | | + | |
: Only applies if ssl_enable is activated. | : Only applies if ssl_enable is activated. | ||
: If activated, all anonymous logins are forced to use a secure SSL connection in order to send and receive data on data connections. | : If activated, all anonymous logins are forced to use a secure SSL connection in order to send and receive data on data connections. | ||
: Default: **NO** | : Default: **NO** | ||
- | | + | |
: Only applies if ssl_enable is activated. | : Only applies if ssl_enable is activated. | ||
: If activated, all anonymous logins are forced to use a secure SSL connection in order to send the password. | : If activated, all anonymous logins are forced to use a secure SSL connection in order to send the password. | ||
: Default: **NO** | : Default: **NO** | ||
- | | + | |
: Only applies if ssl_enable is activated. | : Only applies if ssl_enable is activated. | ||
: If activated, all non-anonymous logins are forced to use a secure SSL connection in order to send and receive data on data connections. | : If activated, all non-anonymous logins are forced to use a secure SSL connection in order to send and receive data on data connections. | ||
: Default: **YES** | : Default: **YES** | ||
- | | + | |
: Only applies if ssl_enable is activated. | : Only applies if ssl_enable is activated. | ||
: If activated, all non-anonymous logins are forced to use a secure SSL connection in order to send the password. | : If activated, all non-anonymous logins are forced to use a secure SSL connection in order to send the password. | ||
: Default: **YES** | : Default: **YES** | ||
- | | + | |
: If enabled, all non-anonymous logins are classed as " | : If enabled, all non-anonymous logins are classed as " | ||
: A guest login is remapped to the user specified in the guest_username setting. | : A guest login is remapped to the user specified in the guest_username setting. | ||
: Default: **NO** | : Default: **NO** | ||
- | | + | |
: \\ If enabled, all user and group information in directory listings will be displayed as " | : \\ If enabled, all user and group information in directory listings will be displayed as " | ||
: Default: **NO** | : Default: **NO** | ||
- | | + | |
: If enabled, an SSL handshake is the first thing expect on all connections (the FTPS protocol). | : If enabled, an SSL handshake is the first thing expect on all connections (the FTPS protocol). | ||
: To support explicit SSL and/or plain text too, a separate vsftpd listener process should be run. | : To support explicit SSL and/or plain text too, a separate vsftpd listener process should be run. | ||
: Default: **NO** | : Default: **NO** | ||
- | | + | |
: \\ If enabled, vsftpd will run in standalone mode. | : \\ If enabled, vsftpd will run in standalone mode. | ||
: This means that vsftpd must not be run from an inetd of some kind. | : This means that vsftpd must not be run from an inetd of some kind. | ||
Ligne 161: | Ligne 161: | ||
: vsftpd itself will then take care of listening for and handling incoming connections. | : vsftpd itself will then take care of listening for and handling incoming connections. | ||
: Default: **YES** | : Default: **YES** | ||
- | | + | |
: Like the listen parameter, except vsftpd will listen on an IPv6 socket instead of an IPv4 one. | : Like the listen parameter, except vsftpd will listen on an IPv6 socket instead of an IPv4 one. | ||
: This parameter and the listen parameter are mutually exclusive. | : This parameter and the listen parameter are mutually exclusive. | ||
: Default: **NO** | : Default: **NO** | ||
- | | + | |
: Controls whether local logins are permitted or not. | : Controls whether local logins are permitted or not. | ||
: If enabled, normal user accounts in /etc/passwd (or wherever your PAM config references) may be used to log in. | : If enabled, normal user accounts in /etc/passwd (or wherever your PAM config references) may be used to log in. | ||
: This must be enable for any non-anonymous login to work, including virtual users. | : This must be enable for any non-anonymous login to work, including virtual users. | ||
: Default: **NO** | : Default: **NO** | ||
- | | + | |
: When enabled, all uploads proceed with a write lock on the upload file. | : When enabled, all uploads proceed with a write lock on the upload file. | ||
: All downloads proceed with a shared read lock on the download file. | : All downloads proceed with a shared read lock on the download file. | ||
: WARNING! Before enabling this, be aware that malicious readers could starve a writer wanting to e.g. append a file. | : WARNING! Before enabling this, be aware that malicious readers could starve a writer wanting to e.g. append a file. | ||
: Default: **YES** | : Default: **YES** | ||
- | | + | |
: \\ When enabled, all FTP requests and responses are logged, providing the option xferlog_std_format is not enabled. | : \\ When enabled, all FTP requests and responses are logged, providing the option xferlog_std_format is not enabled. | ||
: Useful for debugging. | : Useful for debugging. | ||
: Default: **NO** | : Default: **NO** | ||
- | | + | |
: \\ When enabled, this setting will allow the use of "ls -R". | : \\ When enabled, this setting will allow the use of "ls -R". | ||
: This is a minor security risk, because a ls -R at the top level of a large site may consume a lot of resources. | : This is a minor security risk, because a ls -R at the top level of a large site may consume a lot of resources. | ||
: Default: **NO** | : Default: **NO** | ||
- | | + | |
: \\ When enabled, this setting will allow MDTM to set file modification times (subject to the usual access checks). | : \\ When enabled, this setting will allow MDTM to set file modification times (subject to the usual access checks). | ||
: Default: **YES** | : Default: **YES** | ||
- | | + | |
: When enabled, this prevents vsftpd from asking for an anonymous password - the anonymous user will log straight in. | : When enabled, this prevents vsftpd from asking for an anonymous password - the anonymous user will log straight in. | ||
: Default: **NO** | : Default: **NO** | ||
- | no_log_lock | + | ; no_log_lock |
- | When enabled, this prevents vsftpd from taking a file lock when writing to log files. This option should generally not be enabled. It exists to workaround operating system bugs such as the Solaris / Veritas filesystem combination which has been observed to sometimes exhibit hangs trying to lock log files. | + | : \\ When enabled, this prevents vsftpd from taking a file lock when writing to log files. |
+ | : This option should generally not be enabled. | ||
+ | : It exists to workaround operating system bugs such as the Solaris/ | ||
+ | : Default: **NO** | ||
+ | ; one_process_model | ||
+ | : If you have a Linux 2.4 kernel, it is possible to use a different security model which only uses one process per connection. | ||
+ | : It is a less pure security model, but gains you performance. | ||
+ | : You really don't want to enable this unless you know what you are doing, and your site supports huge numbers of simultaneously connected users. | ||
+ | : Default: **NO** | ||
+ | ; passwd_chroot_enable | ||
+ | : \\ If enabled, along with chroot_local_user , then a chroot() jail location may be specified on a per-user basis. | ||
+ | : Each user's jail is derived from their home directory string in / | ||
+ | : Default: **NO** | ||
+ | ; pasv_addr_resolve | ||
+ | : Set to YES if you want to use a hostname (as opposed to IP address) in the pasv_address option. | ||
+ | : Default: **NO** | ||
+ | ; pasv_enable | ||
+ | : Set to NO if you want to disallow the PASV method of obtaining a data connection. | ||
+ | : Default: **YES** | ||
+ | ; pasv_promiscuous | ||
+ | : Set to YES if you want to disable the PASV security check that ensures the data connection originates from the same IP address as the control connection. | ||
+ | : Only enable if you know what you are doing ! | ||
+ | : The only legitimate use for this is in some form of secure tunnelling scheme, or perhaps to facilitate FXP support. | ||
+ | : Default: **NO** | ||
+ | ; port_enable | ||
+ | : Set to NO if you want to disallow the PORT method of obtaining a data connection. | ||
+ | : Default: **YES** | ||
+ | ; port_promiscuous | ||
+ | : Set to YES if you want to disable the PORT security check that ensures that outgoing data connections can only connect to the client. | ||
+ | : Only enable if you know what you are doing ! | ||
+ | : Default: **NO** | ||
+ | ; require_cert | ||
+ | : If set to yes, all SSL client connections are required to present a client certificate. | ||
+ | : The degree of validation applied to this certificate is controlled by validate_cert (Added in v2.0.6). | ||
+ | : Default: **NO** | ||
+ | ; require_ssl_reuse | ||
+ | : If set to yes, all SSL data connections are required to exhibit SSL session reuse (which proves that they know the same master secret as the control channel). | ||
+ | : Although this is a secure default, it may break many FTP clients, so you may want to disable it. | ||
+ | : For a discussion of the consequences, | ||
+ | : Default: **YES** | ||
+ | ; run_as_launching_user | ||
+ | : Set to YES if you want vsftpd to run as the user which launched vsftpd. | ||
+ | : This is useful where root access is not available. | ||
+ | : MASSIVE WARNING! Do NOT enable this option unless you totally know what you are doing, as naive use of this option can create massive security problems. | ||
+ | : Specifically, | ||
+ | : A poor substitute could be to use a deny_file setting such as {/*,*..*}, but the reliability of this cannot compare to chroot, and should not be relied on. | ||
+ | : If using this option, many restrictions on other options apply. | ||
+ | : For example, options requiring privilege such as non-anonymous logins, upload ownership changing, connecting from port 20 and listen ports less than 1024 are not expected to work. | ||
+ | : Other options may be impacted. | ||
+ | : Default: **NO** | ||
+ | ; secure_email_list_enable | ||
+ | : Set to YES if you want only a specified list of e-mail passwords for anonymous logins to be accepted. | ||
+ | : This is useful as a low-hassle way of restricting access to low-security content without needing virtual users. | ||
+ | : When enabled, anonymous logins are prevented unless the password provided is listed in the file specified by the email_password_file setting. | ||
+ | : The file format is one password per line, no extra whitespace. | ||
+ | : The default filename is / | ||
+ | : Default: **NO** | ||
+ | ; session_support | ||
+ | : This controls whether vsftpd attempts to maintain sessions for logins. | ||
+ | : If vsftpd is maintaining sessions, it will try and update utmp and wtmp. | ||
+ | : It will also open a pam_session if using PAM to authenticate, | ||
+ | : You may wish to disable this if you do not need session logging, and you wish to give vsftpd more opportunity to run with less processes and / or less privilege. | ||
+ | : NOTE - utmp and wtmp support is only provided with PAM enabled builds. | ||
+ | : Default: **NO** | ||
+ | ; setproctitle_enable | ||
+ | : \\ If enabled, vsftpd will try and show session status information in the system process listing. | ||
+ | : In other words, the reported name of the process will change to reflect what a vsftpd session is doing (idle, downloading etc). | ||
+ | : You probably want to leave this off for security purposes. | ||
+ | : Default: **NO** | ||
+ | ; ssl_enable | ||
+ | : \\ If enabled, and vsftpd was compiled against OpenSSL, vsftpd will support secure connections via SSL. | ||
+ | : This applies to the control connection (including login) and also data connections. You'll need a client with SSL support too. | ||
+ | : NOTE!! Beware enabling this option. Only enable it if you need it. vsftpd can make no guarantees about the security of the OpenSSL libraries. | ||
+ | : By enabling this option, you are declaring that you trust the security of your installed OpenSSL library. | ||
+ | : Default: **NO** | ||
+ | ; ssl_request_cert | ||
+ | : \\ If enabled, vsftpd will request (but not necessarily require; see require_cert)acertificateonincomingSSLconnections.Normallythis should not cause any trouble at all, but IBM zOS seems to have issues. (New in v2.0.7). | ||
+ | : Default: **YES** | ||
+ | ; ssl_sslv2 | ||
+ | : Only applies if ssl_enable is activated. If enabled, this option will permit SSL v2 protocol connections. TLS v1 connections are preferred. | ||
+ | : Default: **NO** | ||
+ | ; ssl_sslv3 | ||
+ | : Only applies if ssl_enable is activated. If enabled, this option will permit SSL v3 protocol connections. TLS v1 connections are preferred. | ||
+ | : Default: **NO** | ||
+ | ; ssl_tlsv1 | ||
+ | : Only applies if ssl_enable is activated. If enabled, this option will permit TLS v1 protocol connections. TLS v1 connections are preferred. | ||
+ | : Default: **YES** | ||
+ | ; strict_ssl_read_eof | ||
+ | : \\ If enabled, SSL data uploads are required to terminate via SSL, not an EOF on the socket. This option is required to be sure that an attacker did not terminate an upload prematurely with a faked TCP FIN. Unfortunately, | ||
+ | : Default: **NO** | ||
+ | ; strict_ssl_write_shutdown | ||
+ | : \\ If enabled, SSL data downloads are required to terminate via SSL, not an EOF on the socket. This is off by default as I was unable to find a single FTP client that does this. It is minor. All it affects is our ability to tell whether the client confirmed full receipt of the file. Even without this option, the client is able to check the integrity of the download. (New in v2.0.7). | ||
+ | : Default: **NO** | ||
+ | ; syslog_enable | ||
+ | : \\ If enabled, then any log output which would have gone to / | ||
+ | : Default: **NO** | ||
+ | ; tcp_wrappers | ||
+ | : \\ If enabled, and vsftpd was compiled with tcp_wrappers support, incoming connections will be fed through tcp_wrappers access control. Furthermore, | ||
+ | : Default: **NO** | ||
+ | ; text_userdb_names | ||
+ | : By default, numeric IDs are shown in the user and group fields of directory listings. You can get textual names by enabling this parameter. It is off by default for performance reasons. | ||
+ | : Default: **NO** | ||
+ | ; tilde_user_enable | ||
+ | : \\ If enabled, vsftpd will try and resolve pathnames such as ~chris/ | ||
+ | : Default: **NO** | ||
+ | ; use_localtime | ||
+ | : \\ 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. | ||
+ | : Default: **NO** | ||
+ | ; use_sendfile | ||
+ | : An internal setting used for testing the relative benefit of using the sendfile() system call on your platform. | ||
+ | : Default: **YES** | ||
+ | ; userlist_deny | ||
+ | : This option is examined if userlist_enable is activated. If you set this setting to NO, then users will be denied login unless they are explicitly listed in the file specified by userlist_file. When login is denied, the denial is issued before the user is asked for a password. | ||
+ | : Default: **YES** | ||
+ | ; userlist_enable | ||
+ | : \\ If enabled, vsftpd will load a list of usernames, from the filename given by userlist_file. If a user tries to log in using a name in this file, they will be denied before they are asked for a password. This may be useful in preventing cleartext passwords being transmitted. See also userlist_deny. | ||
+ | : Default: **NO** | ||
+ | ; validate_cert | ||
+ | : \\ If set to yes, all SSL client certificates received must validate OK. Self-signed certs do not constitute OK validation. (New in v2.0.6). | ||
+ | : Default: **NO** | ||
+ | ; virtual_use_local_privs | ||
+ | : \\ If enabled, virtual users will use the same privileges as local users. By default, virtual users will use the same privileges as anonymous users, which tends to be more restrictive (especially in terms of write access). | ||
+ | : Default: **NO** | ||
+ | ; write_enable | ||
+ | : This controls whether any FTP commands which change the filesystem are allowed or not. These commands are: STOR, DELE, RNFR, RNTO, MKD, RMD, APPE and SITE. | ||
+ | : Default: **NO** | ||
+ | ; xferlog_enable | ||
+ | : \\ If enabled, a log file will be maintained detailling uploads and downloads. By default, this file will be placed at / | ||
+ | : Default: **NO (but the sample config file enables it)** | ||
+ | ; xferlog_std_format | ||
+ | : \\ If enabled, the transfer log file will be written in standard xferlog format, as used by wu-ftpd. This is useful because you can reuse existing transfer statistics generators. The default format is more readable, however. The default location for this style of log file is / | ||
+ | : Default: **NO** | ||
- | Default: NO | + | ===== Options numériques ===== |
- | one_process_model | + | |
- | If you have a Linux 2.4 kernel, it is possible to use a different security model which only uses one process per connection. It is a less pure security model, but gains you performance. You really don't want to enable this unless you know what you are doing, and your site supports huge numbers of simultaneously connected users. | + | |
- | + | ||
- | Default: NO | + | |
- | passwd_chroot_enable | + | |
- | If enabled, along with chroot_local_user , then a chroot() jail location may be specified on a per-user basis. Each user's jail is derived from their home directory string in / | + | |
- | + | ||
- | Default: NO | + | |
- | pasv_addr_resolve | + | |
- | Set to YES if you want to use a hostname (as opposed to IP address) in the pasv_address option. | + | |
- | + | ||
- | Default: NO | + | |
- | pasv_enable | + | |
- | Set to NO if you want to disallow the PASV method of obtaining a data connection. | + | |
- | + | ||
- | Default: YES | + | |
- | pasv_promiscuous | + | |
- | Set to YES if you want to disable the PASV security check that ensures the data connection originates from the same IP address as the control connection. Only enable if you know what you are doing! The only legitimate use for this is in some form of secure tunnelling scheme, or perhaps to facilitate FXP support. | + | |
- | + | ||
- | Default: NO | + | |
- | port_enable | + | |
- | Set to NO if you want to disallow the PORT method of obtaining a data connection. | + | |
- | + | ||
- | Default: YES | + | |
- | port_promiscuous | + | |
- | Set to YES if you want to disable the PORT security check that ensures that outgoing data connections can only connect to the client. Only enable if you know what you are doing! | + | |
- | + | ||
- | Default: NO | + | |
- | require_cert | + | |
- | If set to yes, all SSL client connections are required to present a client certificate. The degree of validation applied to this certificate is controlled by validate_cert (Added in v2.0.6). | + | |
- | + | ||
- | Default: NO | + | |
- | require_ssl_reuse | + | |
- | If set to yes, all SSL data connections are required to exhibit SSL session reuse (which proves that they know the same master secret as the control channel). Although this is a secure default, it may break many FTP clients, so you may want to disable it. For a discussion of the consequences, | + | |
- | + | ||
- | Default: YES | + | |
- | run_as_launching_user | + | |
- | Set to YES if you want vsftpd to run as the user which launched vsftpd. This is useful where root access is not available. MASSIVE WARNING! Do NOT enable this option unless you totally know what you are doing, as naive use of this option can create massive security problems. Specifically, | + | |
- | + | ||
- | Default: NO | + | |
- | secure_email_list_enable | + | |
- | Set to YES if you want only a specified list of e-mail passwords for anonymous logins to be accepted. This is useful as a low-hassle way of restricting access to low-security content without needing virtual users. When enabled, anonymous logins are prevented unless the password provided is listed in the file specified by the email_password_file setting. The file format is one password per line, no extra whitespace. The default filename is / | + | |
- | + | ||
- | Default: NO | + | |
- | session_support | + | |
- | This controls whether vsftpd attempts to maintain sessions for logins. If vsftpd is maintaining sessions, it will try and update utmp and wtmp. It will also open a pam_session if using PAM to authenticate, | + | |
- | + | ||
- | Default: NO | + | |
- | setproctitle_enable | + | |
- | If enabled, vsftpd will try and show session status information in the system process listing. In other words, the reported name of the process will change to reflect what a vsftpd session is doing (idle, downloading etc). You probably want to leave this off for security purposes. | + | |
- | + | ||
- | Default: NO | + | |
- | ssl_enable | + | |
- | If enabled, and vsftpd was compiled against OpenSSL, vsftpd will support secure connections via SSL. This applies to the control connection (including login) and also data connections. You'll need a client with SSL support too. NOTE!! Beware enabling this option. Only enable it if you need it. vsftpd can make no guarantees about the security of the OpenSSL libraries. By enabling this option, you are declaring that you trust the security of your installed OpenSSL library. | + | |
- | + | ||
- | Default: NO | + | |
- | ssl_request_cert | + | |
- | If enabled, vsftpd will request (but not necessarily require; see require_cert)acertificateonincomingSSLconnections.Normallythis should not cause any trouble at all, but IBM zOS seems to have issues. (New in v2.0.7). | + | |
- | + | ||
- | Default: YES | + | |
- | ssl_sslv2 | + | |
- | Only applies if ssl_enable is activated. If enabled, this option will permit SSL v2 protocol connections. TLS v1 connections are preferred. | + | |
- | + | ||
- | Default: NO | + | |
- | ssl_sslv3 | + | |
- | Only applies if ssl_enable is activated. If enabled, this option will permit SSL v3 protocol connections. TLS v1 connections are preferred. | + | |
- | + | ||
- | Default: NO | + | |
- | ssl_tlsv1 | + | |
- | Only applies if ssl_enable is activated. If enabled, this option will permit TLS v1 protocol connections. TLS v1 connections are preferred. | + | |
- | + | ||
- | Default: YES | + | |
- | strict_ssl_read_eof | + | |
- | If enabled, SSL data uploads are required to terminate via SSL, not an EOF on the socket. This option is required to be sure that an attacker did not terminate an upload prematurely with a faked TCP FIN. Unfortunately, | + | |
- | + | ||
- | Default: NO | + | |
- | strict_ssl_write_shutdown | + | |
- | If enabled, SSL data downloads are required to terminate via SSL, not an EOF on the socket. This is off by default as I was unable to find a single FTP client that does this. It is minor. All it affects is our ability to tell whether the client confirmed full receipt of the file. Even without this option, the client is able to check the integrity of the download. (New in v2.0.7). | + | |
- | + | ||
- | Default: NO | + | |
- | syslog_enable | + | |
- | If enabled, then any log output which would have gone to / | + | |
- | + | ||
- | Default: NO | + | |
- | tcp_wrappers | + | |
- | If enabled, and vsftpd was compiled with tcp_wrappers support, incoming connections will be fed through tcp_wrappers access control. Furthermore, | + | |
- | + | ||
- | Default: NO | + | |
- | text_userdb_names | + | |
- | By default, numeric IDs are shown in the user and group fields of directory listings. You can get textual names by enabling this parameter. It is off by default for performance reasons. | + | |
- | + | ||
- | Default: NO | + | |
- | tilde_user_enable | + | |
- | If enabled, vsftpd will try and resolve pathnames such as ~chris/ | + | |
- | + | ||
- | Default: NO | + | |
- | use_localtime | + | |
- | 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. | + | |
- | + | ||
- | Default: NO | + | |
- | use_sendfile | + | |
- | An internal setting used for testing the relative benefit of using the sendfile() system call on your platform. | + | |
- | + | ||
- | Default: YES | + | |
- | userlist_deny | + | |
- | This option is examined if userlist_enable is activated. If you set this setting to NO, then users will be denied login unless they are explicitly listed in the file specified by userlist_file. When login is denied, the denial is issued before the user is asked for a password. | + | |
- | + | ||
- | Default: YES | + | |
- | userlist_enable | + | |
- | If enabled, vsftpd will load a list of usernames, from the filename given by userlist_file. If a user tries to log in using a name in this file, they will be denied before they are asked for a password. This may be useful in preventing cleartext passwords being transmitted. See also userlist_deny. | + | |
- | + | ||
- | Default: NO | + | |
- | validate_cert | + | |
- | If set to yes, all SSL client certificates received must validate OK. Self-signed certs do not constitute OK validation. (New in v2.0.6). | + | |
- | + | ||
- | Default: NO | + | |
- | virtual_use_local_privs | + | |
- | If enabled, virtual users will use the same privileges as local users. By default, virtual users will use the same privileges as anonymous users, which tends to be more restrictive (especially in terms of write access). | + | |
- | + | ||
- | Default: NO | + | |
- | write_enable | + | |
- | This controls whether any FTP commands which change the filesystem are allowed or not. These commands are: STOR, DELE, RNFR, RNTO, MKD, RMD, APPE and SITE. | + | |
- | + | ||
- | Default: NO | + | |
- | xferlog_enable | + | |
- | If enabled, a log file will be maintained detailling uploads and downloads. By default, this file will be placed at / | + | |
- | + | ||
- | Default: NO (but the sample config file enables it) | + | |
- | xferlog_std_format | + | |
- | If enabled, the transfer log file will be written in standard xferlog format, as used by wu-ftpd. This is useful because you can reuse existing transfer statistics generators. The default format is more readable, however. The default location for this style of log file is / | + | |
- | + | ||
- | Default: NO | + | |
- | + | ||
- | ====== Options numériques | + | |
Below is a list of numeric options. A numeric option must be set to a non negative integer. Octal numbers are supported, for convenience of the umask options. To specify an octal number, use 0 as the first digit of the number. | Below is a list of numeric options. A numeric option must be set to a non negative integer. Octal numbers are supported, for convenience of the umask options. To specify an octal number, use 0 as the first digit of the number. | ||
- | accept_timeout | + | ; accept_timeout |
- | The timeout, in seconds, for a remote client to establish connection with a PASV style data connection. | + | : |
- | + | : | |
- | | + | ; |
- | anon_max_rate | + | : |
- | The maximum data transfer rate permitted, in bytes per second, for anonymous clients. | + | : |
- | + | ; | |
- | | + | : |
- | anon_umask | + | : |
- | The value that the umask for file creation is set to for anonymous users. NOTE! If you want to specify octal values, remember the " | + | ; |
- | + | : | |
- | | + | : |
- | chown_upload_mode | + | ; |
- | The file mode to force for chown()ed anonymous uploads. (Added in v2.0.6). | + | : |
- | + | : | |
- | | + | ; |
- | connect_timeout | + | : |
- | The timeout, in seconds, for a remote client to respond to our PORT style data connection. | + | : |
- | + | ; | |
- | | + | : |
- | data_connection_timeout | + | : |
- | The timeout, in seconds, which is roughly the maximum time we permit data transfers to stall for with no progress. If the timeout triggers, the remote client is kicked off. | + | ; |
- | + | : | |
- | | + | : |
- | delay_failed_login | + | ; |
- | The number of seconds to pause prior to reporting a failed login. | + | : |
- | + | : | |
- | | + | ; |
- | delay_successful_login | + | : |
- | The number of seconds to pause prior to allowing a successful login. | + | : |
- | + | ||
- | | + | |
- | file_open_mode | + | |
- | The permissions with which uploaded files are created. Umasks are applied on top of this value. You may wish to change to 0777 if you want uploaded files to be executable. | + | |
- | + | ||
- | | + | |
- | ftp_data_port | + | |
- | The port from which PORT style connections originate (as long as the poorly named connect_from_port_20 is enabled). | + | |
- | + | ||
- | | + | |
idle_session_timeout | idle_session_timeout | ||
The timeout, in seconds, which is the maximum time a remote client may spend between FTP commands. If the timeout triggers, the remote client is kicked off. | The timeout, in seconds, which is the maximum time a remote client may spend between FTP commands. If the timeout triggers, the remote client is kicked off. | ||
Ligne 411: | Ligne 398: | ||
Default: 0 (let vsftpd pick a sensible setting) | Default: 0 (let vsftpd pick a sensible setting) | ||
- | ====== Options de chaîne | + | ===== Options de chaîne ===== |
Below is a list of string options. | Below is a list of string options. | ||
Ligne 544: | Ligne 531: | ||
Default: / | Default: / | ||
- | ====== Voir aussi ====== | + | ===== Voir aussi ===== |
* **(en)** [[http:// | * **(en)** [[http:// |