mod_core
AccessDenyMsg
AccessDenyMsg
AccessDenyMsgCustomise the response on failed authenticationAccessDenyMsgDefault
Dependent on login type
Context
server config, <VirtualHost>, <Anonymous>, <Global>
Module
mod_core
Compatibility
1.2.2 and later
Description
Normally, a 530 response message is sent to an FTP client immediately after
a failed authentication attempt, with a standard message indicating the the
reason of failure. In the case of a wrong password, the reason is usually
"Login incorrect." It is this message can be customized with the AccessDenyMsg
directive. In the message argument, the magic cookie '%u' is replaced with
the username specified by the client during login.See alsoExamples
AccessDenyMsg "Guest access denied for %u."
mod_core
AccessGrantMsg
AccessGrantMsg
AccessGrantMsgCustomise the response on successful authenticationAccessGrantMsgDefault
Dependent on login type
Context
server config, <VirtualHost>, <Anonymous>, <Global>
Module
mod_core
Compatibility
0.99.0pl5 and later
Description
Normally, a 230 response message is sent to an FTP client immediately after
authentication, with a standard message indicating that the user has either
logged in or that anonymous access has been granted. This message
can be customized with the AccessGrantMsg directive. In the message argument,
the magic cookie '%u' is replaced with the username specified by the client
during login.See alsoExamples
AccessGrantMsg "Guest access granted for %u."
mod_core
Allow
Allow
AllowAccess control directiveAllowDefault
Allow from all
Context
<Limit>
Module
mod_core
Compatibility
0.99.0pl6 and later
Description
The Allow directive is used inside a <Limit> context to explicitly
specify which hosts and/or networks have access to the commands or
operations being limited. Allow is typically used in conjunction
with Order and Deny in order to create sophisticated (or perhaps
not-so-sophisticated) access control rules. Allow takes an optional
first argument; the keyword from. Using from is purely cosmetic. The
remaining arguments are expected to be a list of hosts and networks which
will be explicitly granted access. The magic keyword all can be used to
indicate that all hosts will explicitly be granted access (analogous to
the AllowAll directive, except with a lower priority). Additionally, the
magic keyword none can be used to indicate that no hosts or networks
will be explicitly granted access (although this does not prevent
them from implicitly being granted access). If all or none is used,
no other hosts or networks can be supplied. Host and network addresses
can be specified by name or numeric address. For security reasons, it is
recommended that all address information be supplied numerically. Relying
solely on named addresses causes security to depend a great deal upon
DNS servers which may themselves be vulnerable to attack or spoofing.
Numeric addresses which specify an entire network should end in a
trailing period (i.e. 10.0.0. for the entire 10.0.0 subnet). Named
address which specify an entire network should begin with a trailing
period (i.e. .proftpd.net for the entire proftpd.net domain).
See also
Allow
Order
Limit
Examples
<Limit LOGIN>
Order allow,deny
Allow from 128.44.26.,128.44.26.,myhost.mydomain.edu,.trusted-domain.org
Deny from all
</Limit>
mod_core
AllowAll
AllowAll
AllowAllAllow all clients AllowAllDefault
Default is to implicitly AllowAll, but not explicitly
Context
<Directory>, <Anonymous>, <Limit>, .ftpaccess
Module
mod_core
Compatibility
0.99.0 and later
Description
The AllowAll directive explicitly allows access to a <Directory>,
<Anonymous> or <Limit> block. Although proftpd's default
behavior is to allow access to a particular object, the default is
an implicit allow. AllowAll creates an explicit allow, overriding any
higher level denial directives.See also
DenyAll
Examples
mod_site
AllowChmod
AllowChmod
AllowChmodEnable the CHMOD command (deprecated)AllowChmodDefault
true
Context
server config, <Directory>, <Global>, <VirtualHost>, <Anonymous>, .ftpaccess
Module
mod_site
Compatibility
1.2.0rc1 and later -- Deprecated
DescriptionThis directive is deprecated, please use >Limit SITE_CHMOD<
instead.
AllowChmod allows control over whether the "SITE CHMOD"
command is allowed to clients.See alsoExamples
AllowChmod false
mod_core
AllowFilter
AllowFilter
AllowFilterRegular expression of command arguments to be acceptedAllowFilterDefault
None
Context
server config, <VirtualHost>, <Anonymous>, <Global>
Module
mod_core
Compatibility
1.2.0pre7 and later
DescriptionAllowFilter allows the configuration of a regular expression
that must be matched for all command arguments sent to ProFTPD. It is
extremely useful in controlling what characters may be sent in a
command to ProFTPD, preventing some possible types of attacks against
ProFTPD. The regular expression is applied against the arguments to
the command sent by the client, so care must be taken when creating a
proper regex. Commands that fail the regex match result in a
"Forbidden command" error being returned to the client. If the
regular-expression argument contains whitespace, it must be enclosed
in quotes.See also
DenyFilter
Examples
# Only allow commands containing alphanumeric characters and whitespace
AllowFilter "^[a-zA-Z0-9 ,]*$"
mod_core
AllowForeignAddress
AllowForeignAddress
AllowForeignAddressControl the use of the PORT commandAllowForeignAddressDefault
AllowForeignAddress off
Context
server config, <VirtualHost>, <Anonymous>, <Global>
Module
mod_core
Compatibility
1.1.7 and later
Description
Normally, proftpd disallows clients from using the ftp PORT command with
anything other than their own address (the source address of the ftp
control connection), as well as preventing the use of PORT to specify
a low-numbered (< 1024) port. In either case, the client is sent an
"Invalid port" error and a message is syslog'd indicating either
"address mismatch" or "bounce attack". By enabling
this directive, proftpd will allow clients to transmit foreign data
connection addresses that do not match the client's address. This allows
such tricks as permitting a client to transfer a file between two FTP
servers without involving itself in the actual data connection. Generally
it's considered a bad idea, security-wise, to permit this sort of thing.
AllowForeignAddress only affects data connection addresses; not tcp
ports. There is no way (and no valid reason) to allow a client to use
a low-numbered port in its PORT command.See alsoExamples
mod_core
AllowGroup
AllowGroup
AllowGroupGroup based allow rulesAllowGroupDefault
None
Context
<Limit>
Module
mod_core
Compatibility
1.1.1 and later
Description
AllowGroup specifies a group-expression that is specifically
permitted within the context of the <Limit> block it is applied
to. group-expression has the same format as that used in DefaultRoot, in
that it should contain a comma separated list of groups or "not"
groups (by prefixing a group name with the `!' character) that are to
be allowed access to the block. The expression is parsed as a boolean
"and" list, meaning that ALL elements of the expression must
evaluate to logically true in order for the explicit allow to apply.
See also
DenyGroup,
DenyUser,
AllowUser
Examples
mod_log
AllowLogSymlinks
Allow
AllowLogSymlinksPermit logging to symlinked filesAllowLogSymlinksDefault
AllowLogSymlinks off
Context
server config, <VirtualHost>, <Global>
Module
mod_log
Compatibility
1.2.2rc2 and later
Description
By default, the server will the path of any configured SystemLog, any configured
TransferLogs, and any configured ExtendedLogs to see if they are symbolic
links. If the paths are symbolic links, the server will refuse to log to that
link unless explicitly configured to do so via this directive.
Security note:
Security note: this behaviour should not be allowed unless for
a very good reason. By allowing the server to open symbolic links with
its root privileges, you are allowing a potential symlink attack where
the server could be tricked into overwriting arbitrary system files.
You have been warned.
See alsoExamples
AllowLogSymlinks on
mod_core
AllowOverwrite
AllowOverwrite
AllowOverwriteEnable files to be overwrittenAllowOverwriteDefault
AllowOverwrite off
Context
server config, <VirtualHost>, <Anonymous>, <Directory>, <Global>, .ftpaccess
Module
mod_core
Compatibility
0.99.0 and later
Description
The AllowOverwrite directive permits newly transfered files to overwrite
existing files. By default, ftp clients cannot overwrite existing files.See alsoExamples
mod_core
AllowRetrieveRestart
AllowRetrieveRestart
AllowRetrieveRestartAllow clients to resume downloadsAllowRetrieveRestartDefault
AllowRetrieveRestart on
Context
server config, <VirtualHost>, <Anonymous>, <Directory>, <Global>, .ftpaccess
Module
mod_core
Compatibility
0.99.0 and later
Description
The AllowRetrieveRestart directive permits or denies clients from
performing "restart" retrieve file transfers via the FTP
REST command. By default this is enabled, so that clients may resume
interrupted file transfers at a later time without losing previously
collected data.See also
AllowStoreRestart
Examples
mod_core
AllowStoreRestart
AllowStoreRestart
AllowStoreRestartAllow clients to resume uploadsAllowStoreRestartDefault
AllowStoreRestart off
Context
server config, <VirtualHost>, <Anonymous>, <Directory>, <Global>, .ftpaccess
Module
mod_core
Compatibility
0.99.0 and later
Description
The AllowStoreRestart directive permits or denies clients from
"restarting" interrupted store file transfers (those sent
from client to server). By default restarting (via the REST command) is
not permitted when sending files to the server. Care should be taken to
disallow anonymous ftp "incoming" transfers to be restarted,
as this will allow clients to corrupt or increase the size of previously
stored files (even if not their own).
The REST (Restart STOR) command is automatically blocked when HiddenStor is
enabled, with the server returning a 501 error code to the client.
See also
AllowRetrieveRestart
DeleteAbortedStores
HiddenStor
Examples
mod_core
AllowUser
AllowUser
AllowUserUser based allow rulesAllowUserDefault
None
Context
<Limit>
Module
mod_core
Compatibility
1.1.7 and later
Description
AllowUser specifies a user-expression that is specifically
permitted access within the context of the <Limit>
block it is applied to. user-expression has a similar
syntax as that used in AllowGroup, in that it should
contain a comma delimited list of users or "not" users (by prefixing
a user name with the `!' character) that are to be allowed access to the block.
The expression is parsed as a boolean "and" list, meaning that ALL
elements of the expression must evaluate to logically true in order to the explicit
allow to apply.See also
DenyUser
DenyGroup
AllowGroup
Examples
mod_ratio
AnonRatio
AnonRatio
AnonRatioRatio directiveAnonRatioDefault
None known
Context
<Directory>, <Anonymous>, <Limit>,.ftpaccess
Module
mod_ratio
Compatibility
at least 1.2.0 and later
Description
The AnonRatio directive ....See also
AnonRatio
Examples
mod_core
AnonRequirePassword
AnonRequirePassword
AnonRequirePasswordMake anonymous users supply a valid passwordAnonRequirePasswordDefault
AnonRequirePassword off
Context
<Anonymous>
Module
mod_core
Compatibility
0.99.0 and later
Description
Normally, anonymous FTP logins do not require the client to authenticate themselves
via the normal method of a transmitted cleartext password which is hashed and
matched against an existing system user's password. Instead, anonymous logins
are expected to enter their e-mail address when prompted for a password. Enabling
the AnonRequirePassword directive requires anonymous logins to enter a valid
password which must match the password of the user that the anonymous daemon
runs as. However using AuthUsingAlias
authentication can be matched against the password of the login username.
This can be used to create "guest" accounts, which function
exactly as normal anonymous logins do (and thus present a
"chrooted"
protected file system to the client), but require a valid password on the server's
host system.See also
AnonymousGroup
AuthAliasOnly
AuthUsingAlias
Examples
Example of a "guest" account configuration:
<Anonymous ~roger>
User roger
Group other
UserAlias proftpd roger
AnonRequirePassword on
# Deny write operations to all directories, underneath root-dir
# Default is to allow, so we don't need a <Limit> for read operations.
<Directory *>
<Limit WRITE>
DenyAll
</Limit>
</Directory>
# Deny all read/write operations in incoming. Because these are command-group
# limits, we can explicitly permit certain operations which will take precedence
# over our group limit.
<Directory incoming>
<Limit READ WRITE>
DenyAll
</Limit>
# The only command allowed in incoming is STOR (transfer file from client
to server)
<Limit STOR>
AllowAll
</Limit>
</Directory>
</Anonymous>
mod_core
Anonymous
Anonymous
AnonymousDefine an anonymous serverAnonymousDefault
None
Context
server config,<VirtualHost>, <Global>
Module
mod_core
Compatibility
0.99.0 and later
Description
The Anonymous configuration block is used to create an anonymous FTP
login, and is terminated by a matching </Anonymous> directive. The
root-directory parameters specifies which directory the daemon will
first chdir to, and then chroot, immediately after login. Once the chroot
operation successfully completes, higher level directories are no longer
accessible to the running child daemon (and thus the logged in user). By
default, proftpd assumes an anonymous login if the remote client attempts
to login as the currently running user; unless the current user is root,
in which case anonymous logins are not allowed regardless of the presence
of an <Anonymous> block. 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 <Anonymous>
block, the daemon permanently switches to the specified uid/gid before
chroot()ing. Normally, anonymous logins are not required to authenticate
with a password, but are expected to enter a valid e-mail address in place
of a normal password (which is logged). If this behavior is undesirable
for a given <Anonymous> configuration block, it can be overridden
via the AnonRequirePassword directive.
Note: Chroot()ed anonymous directories do not need to have supplemental
system files in them, nor do they need to have any sort of specific
directory structure. This is because proftpd is designed to acquire as
much system information as possible before the chroot, and to leave open
those files which are needed for normal operation and reside outside
the new root directory.
See alsoExamples
Example of a typical anonymous FTP configuration:
<Anonymous /home/ftp>
User ftp # After anonymous login, daemon runs as user ftp.
Group ftp # After anonymous login, daemon runs as group ftp.
UserAlias anonymous ftp # Client login as 'anonymous' is aliased to 'ftp'.
# Deny write operations to all directories, underneath root-dir
# Default is to allow, so we don't need a <Limit> for read operations.
<Directory *>
<Limit WRITE>
DenyAll
</Limit>
</Directory>
<Directory incoming>
<Limit READ WRITE>
DenyAll
</Limit>
<Limit STOR>
AllowAll
</Limit>
</Directory>
</Anonymous>
mod_core
AnonymousGroup
AnonymousGroup
AnonymousGroupTreat group members as anonymous usersAnonymousGroupDefault
None
Context
server config, <VirtualHost>, <Global>
Module
mod_core
Compatibility
1.1.3 and later
Description
The AnonymousGroup directive specifies a group-expression to which all
matching users will be considered anonymous logins. The group-expression
argument is a boolean logically ANDed list of groups to which the user
must be a member of (or non-member if the group name is prefixed with
a `!' character). For more information on group-expressions see the
DefaultRoot directive. If the authenticating user is matched by an
AnonymousGroup directive, no valid password is required, and a special
dynamic anonymous configuration is created, with the user's home directory
as the default root directory. If a DefaultRoot directive also applies
to the user, this directory is used instead of the user's home dir.
Great care should be taken when using AnonymousGroup, as improper
configuration can open up user home directories to full read/write access
to the entire world.See also
AuthAliasOnly
AuthUsingAlias
AnonRequirePassword
DefaultRoot
Examples
mod_core
AuthAliasOnly
AuthAliasOnly
AuthAliasOnlyAllow only aliased login namesAuthAliasOnlyDefault
AuthAliasOnly off
Context
server config, <VirtualHost>, <Anonymous>, <Global>
Module
mod_core
Compatibility
1.1.3 and later
Description
AuthAliasOnly restricts authentication to "aliased" logins only;
i.e. those usernames provided by clients which are "mapped"
to a real userid by the UserAlias directive. Turning AuthAliasOnly `on'
in a particular context will cause proftpd to completely ignore all
non-aliased logins for the entire context. If no contexts are available
without AuthAliasOnly set to `on', proftpd rejects the client login and
sends an appropriate message to syslog.See also
AnonymousGroup
AuthUsingAlias
AnonRequirePassword
UserAlias
Examples
mod_unixpw
AuthGroupFile
AuthGroupFile
AuthGroupFileSpecify alternate group fileAuthGroupFileDefault
None
Context
server config, <VirtualHost>, <Global>
Module
mod_unixpw
Compatibility
1.0.3/1.1.1 and later
Description
AuthGroupFile specifies an alternate groups file, having the same
format as the system /etc/group file, and if specified is used
during authentication and group lookups for directory/access control
operations. The path argument should be the full path to the specified
file. AuthGroupFile can be configured on a per-VirtualHost basis, so
that virtual FTP servers can each have their own authentication database
(most often used in conjunction with AuthUserFile).
Note that this file need not reside inside a chroot()ed directory
structure for Anonymous or DefaultRoot logins, as it is held open for
the duration of client connections.See also
AuthUserFile
Examples
mod_pam
AuthPAM
AuthPAM
AuthPAMEnable/Disable PAM authenticationAuthPAMDefault
on
Context
server config,<VirtualHost>, <Global>
Module
mod_pam
Compatibility
1.2.0rc1 and later
Description
This directive determines whether PAM is used as an authentication
method by ProFTPD. Enabled by default to fit in with the design
policy of using PAM as the primary authentication mechanism.See alsoExamples
mod_unixpw
AuthPAMAuthoritative
AuthPAMAuthoritative
AuthPAMAuthoritativeSet whether PAM is the authoritive authentication schemeAuthPAMAuthoritativeDefault
off
Context
server config,<VirtualHost>, <Global>
Module
mod_pam
Compatibility
1.2.0pre3 and later
Description
This directive allows you to control whether or not PAM is the ultimate
authority on authentication. Setting this directive to on will cause
authentication to fail if PAM authentication fails. The default setting,
off, allows other modules and directives such as AuthUserFile and friends
to authenticate users, should PAM authentication fail. If you are having
problems with PAM and using other directives like AuthUserFile, set this
directive to off.See alsoExamples
mod_pam
AuthPAMConfig
AuthPAMConfig
AuthPAMConfigSelect PAM service nameAuthPAMConfigDefault
ftp
Context
server config,<VirtualHost>, <Global>
Module
mod_pam
Compatibility
1.2.0rc1 and later
Description
This directive allows you to specify the PAM service name used in
authentication. PAM allows you to specify a service name to use when
authenticating. This allows you to configure different PAM service names
to be used for different virtual hosts. The directive was renamed from
PAMConfig post 1.2.0 pre10.
See alsoExamples
# Virtual host foobar authenticates differently than the rest
AuthPAMConfig foobar
# This assumes, that you have a PAM service named foobar
# configured in your /etc/pam.conf file or /etc/pam.d directory.
mod_unixpw
AuthUserFile
AuthUserFile
AuthUserFileSpecify alternate passwd fileAuthUserFileDefault
None
Context
server config,<VirtualHost>, <Global>
Module
mod_unixpw
Compatibility
1.0.3/1.1.1 and later
Description
AuthUserFile specifies an alternate passwd file, having the same
format as the system /etc/passwd file, and if specified is used
during authentication and user lookups for directory/access control
operations. The path argument should be the full path to the specified
file. AuthUserFile can be configured on a per-VirtualHost basis, so
that virtual FTP servers can each have their own authentication database
(most often used in conjunction with AuthGroupFile).
Note that this file need not reside inside a chroot()ed directory
structure for Anonymous or DefaultRoot logins, as it is held open for
the duration of client connections.
See also
AuthGroupFile
Examples
mod_core
AuthUsingAlias
AuthUsingAlias
AuthUsingAliasFIXME FIXMEAuthUsingAliasDefault
AuthUsingAlias off
Context
<Anonymous>
Module
mod_core
Compatibility
1.2.0pre9 and later
Description
Normally, when the AnonRequirePassword directive is used, the
authentication is done using the password entry of the daemon
process. However under certain circumstances it may be required for the
authentication to be done using the login username & password instead.
See also
AnonymousGroup
AuthAliasOnly
AnonRequirePassword
Examples
An example of an Anonymous configuration using
AuthUsingAlias
# Basic Read-Only Anonymous Configuration.
<Anonymous /home/ftp>
UserAlias anonymous nobody
UserAlias ftp nobody
AuthAliasOnly on
<Limit WRITE>
DenyAll
</Limit>
</Anonymous>
# Give Full Read-Write Anonymous Access to certain users
<Anonymous /home/ftp>
AnonRequirePassword on
AuthAliasOnly on
AuthUsingAlias on
# The list of authorized users.
# user/pass lookup is for each user, not password entry
# of server uid ('nobody' in this example).
UserAlias fred nobody
UserAlias joe nobody
<Limit ALL>
AllowAll
</Limit>
</Anonymous>
mod_core
Bind
Bind
BindBind the server or Virtualhost to a specific IP addressBindDefault
None
Context
server config, <VirtualHost>
Module
mod_core
Compatibility
1.1.6 and later
Description
The Bind directive allows additional IP addresses to be bound to a main
or VirtualHost configuration. Multiple Bind directives can be used to
bind multiple addresses. The address argument should be either a fully
qualified domain name or a numeric dotted-quad IP address. Incoming
connections destined to an additional address added by Bind are serviced
by the context containing the directive. Additionally, if SocketBindTight
is set to on, a specific listen connection is created for each additional
address.See alsoExamples
mod_ratio
ByteRatioErrMsg
ByteRatioErrMsg
ByteRatioErrMsgRatio directiveByteRatioErrMsgDefault
None known
Context
<Directory>, <Anonymous>, <Limit>,.ftpaccess
Module
mod_ratio
Compatibility
at least 1.2.0 and later
Description
The ByteRatioErrMsg directive ....
Example:
ByteRatioErrMsgSee alsoExamples
mod_core
CDPath
CDPath
CDPathSets "search paths" for the cd commandCDPathDefault
None
Context
server config, <VirtualHost>, <Anonymous>, <Global>
Module
mod_core
Compatibility
1.2.0pre2 and later
Description
Adds an entry to a search path that is used when changing directories. For
example:
CDPath /home/public
CDPath /var/devel
This allows a user to cd into any directory directly under /home/public or /var/devel,
provided they have the appropriate rights. So, if /home/public/proftpd exists,
cd proftpd will bring the user to that directory, regardless of where
they currently are in the directory tree.See alsoExamples
mod_core
Class
Class
ClassDefinition statements for class based trackingClassDefault
None
Context
server config, <VirtualHost>
Module
mod_core
Compatibility
1.2.0pre9 and later
Description
Controls class based access. Class base access allows each connecting IP to
be classified into a separate class. Each class has its own maximum number
of connections. limit sets the maximum number of connections (default is 100)
for that class name, regex sets a hostname regex (POSIX) for
inclusion in the class and ip sets an IP/netmask based inclusion.
See alsoExamples
Classes on
Class local limit 100
Class default limit 10
Class local regex .*foo.com
Class local ip 172.16.1.0/24
This creates two classes, local and default, with local being everything in
*.foo.com and 172.16.1.* combined.
mod_core
Classes
Classes
ClassesEnable Class based connection trackingClassesDefault
Off
Context
server config, <VirtualHost>
Module
mod_core
Compatibility
1.2.0pre9 and later
Description
Controls class based access. Enables class based access control.
see: ClassSee alsoExamples
For examples, see
Class
mod_core
CommandBufferSize
CommandBufferSize
CommandBufferSizeLimit the maximum command lengthCommandBufferSizeDefault
None
Context
server config, <VirtualHost>, <Global>
Module
mod_core
Compatibility
1.2.0pre7 and later
Description
The CommandBufferSize directive controls the maximum command length permitted
to be sent to the server. This allows you to effectively control what the longest
command the server may accept it, and can help protect the server from various
Denial of Service or resource-consumption attacks. See alsoExamples
mod_ratio
CwdRatioMsg
CwdRatioMsg
CwdRatioMsgRatio directiveCwdRatioMsgDefault
None known
Context
<Directory>, <Anonymous>, <Limit>,.ftpaccess
Module
mod_ratio
Compatibility
at least 1.2.0 and later
Description
The CwdRatioMsg directive ....
Example:
CwdRatioMsgSee alsoExamples
mod_auth
DefaultChdir
DefaultChdir
DefaultChdirSet starting directory for FTP sessionsDefaultChdirDefault
~
Context
server config, <VirtualHost>, <Anonymous>, <Global>
Module
mod_auth
Compatibility
1.2.0pre2 and later
Description
Determines the directory a user is placed in after logging in.
By default, the user is put in their home directory. The specified
directory can be relative to the user's home directory.
NOTE: if the specified directory is not available
the user will not be able to log in.See also
DefaultRoot
Examples
mod_quota
DefaultQuota
DefaultQuota
DefaultQuotaSets the default quotaDefaultQuotaDefault
0
Context
server, <VirtualHost>, <Anonymous>
Module
mod_quota
Compatibility
at least 1.2.0 and later
Description
The DefaultQuota directive sets the default quota in bytes, this
value is used if the .quota file does not exist.See also
Quotas
Examples
#
# Set default to 1kb
#
DefaultQuota 1024
mod_auth
DefaultRoot
DefaultRoot
DefaultRootSets default chroot directoryDefaultRootDefault
DefaultRoot /
Context
server config, <VirtualHost>, <Global>
Module
mod_auth
Compatibility
0.99.0pl7 and later
Description
The DefaultRoot directive controls the default root directory assigned
to a user upon login. If DefaultRoot is set to a directory other than
"/", a chroot operation is performed immediately after a client
authenticates. This can be used to effectively isolate the client from
a portion of the host system filespace. The specified root directory
must begin with a / or can be the magic character '~'; meaning that the
client is chroot jailed into their home directory.
If the DefaultRoot directive specifies a directory which disallows
access to the logged-in user's home directory, the user's current
working directory after login is set to the DefaultRoot instead of their
normal home directory. DefaultRoot cannot be used in <Anonymous>
configuration blocks, as the <Anonymous> directive explicitly
contains a root directory used for Anonymous logins. The special
character '~' is replaced with the authenticating user's home directory
immediately after login. Note that the default root may be a subdirectory
of the home directory, such as "~/anon-ftp".
The optional group-expression argument can be used to restrict the
DefaultRoot directive to a unix group, groups or subset of groups. The
expression takes the format: [!]group-name1[,[!]group-name2[,...]]. The
expression is parsed in a logical boolean AND fashion, such that each
member of the expression must evaluate to logically TRUE in order for
the DefaultRoot directive to apply. The special character '!' is used
to negate group membership.
Care should be taken when using DefaultRoot. Chroot "jails"
should not be used as methods for implementing general system security
as there are potentially ways that a user can "escape" the jail.
See alsoExamples
Example of a DefaultRoot configuration:
ServerName "A test ProFTPD Server"
ServerType inetd
User ftp
Group ftp
#
# This causes proftpd to perform a chroot into the authenticating user's directory
immediately after login.
# Once this happens, the user is unable to "see" higher level directories.
# Because a group-expression is included, only users who are a member of
# the group 'users' and NOT a member of 'staff' will have their default
# root directory set to '~'.
DefaultRoot ~ users,!staff
...
mod_core
DefaultServer
DefaultServer
DefaultServerSet the default serverDefaultServerDefault
DefaultServer off
Context
server config,<VirtualHost>
Module
mod_core
Compatibility
0.99.0pl6 and later
Description
The DefaultServer directive controls which server configuration is used as
the default when an incoming connection is destined for an IP address which
is neither the host's primary IP address or one of the addresses specified in
a <VirtualHost> configuration block. Normally such
"unknown" connections are issued a "no server available to service
your request" message and disconnected. When DefaultServer is turned on
for either the primary server configuration or a virtual server, all unknown
destination connections are serviced by the default server. Only a single server
configuration can be set to default.See alsoExamples
mod_core
DefaultTransferMode
DefaultTransferMode
DefaultTransferModeSet the default method of data transferDefaultTransferModeDefault
DefaultTransferMode ascii
Context
server config, <VirtualHost>, <Global>
Module
mod_core
Compatibility
1.2.0pre9 and later
Description
DefaultTransferMode sets the default transfer mode of the server. By default,
carriage-return/linefeed translation will be performed (ASCII mode).See alsoExamples
mod_core
DeferWelcome
DeferWelcome
DeferWelcomeDon't show welcome message until user has authenticatedDeferWelcomeDefault
DeferWelcome off
Context
server config, <VirtualHost>, <Global>
Module
mod_core
Compatibility
0.99.0 and later
Description
The DeferWelcome directive configures a master or
virtual server to delay transmitting the
ServerName and address to new connections,
until a client has successfully authenticated. If enabled, the initial welcome
message will be exceedingly generic and will not give away any type of information
about the host that the daemon is actively running on. This can be used by security-conscious
administrators to limit the amount of "probing" possible from non-trusted
networks/hosts.See also
ServerIdent
ServerName
Examples
mod_core
DeleteAbortedStores
DeleteAbortedStores
DeleteAbortedStoresEnable automatic deletion of partially uploaded filesDeleteAbortedStoresDefault
off
Context
server, <VirtualHost>, <Directory>, <Anonymous>, <Global>, .ftpaccess
Module
mod_core
Compatibility
1.2.0rc2 and later
Description
The DeleteAbortedStores directive controls whether ProFTPD
deletes partially uploaded files if the transfer is stopped via
the ABOR command rather than a connection failure.See also
HiddenStor
Examples
mod_core
Deny
Deny
DenyAccess control directiveDenyDefault
None
Context
<Limit>
Module
mod_core
Compatibility
0.99.0pl6 and later
Description
The Deny directive is used to create a list of hosts and/or networks which
will explicitly be denied access to a given <Limit> context block. The magic keywords all
and none can be used to indicate that all hosts are
denied access, or that no hosts are explicitly denied (respectively). For more
information on the syntax and usage of Deny see: Allow
and Order.See also
Allow
Order
Limit
Examples
mod_core
DenyAll
DenyAll
DenyAllDeny all clientsDenyAllDefault
None
Context
<Directory>, <Anonymous>, <Limit>, .ftpaccess
Module
mod_core
Compatibility
0.99.0 and later
Description
The DenyAll directive is analogous to a combination of "order
deny,allow <cr> deny from all", with the exception that it
has a higher precendance when parsed. It is provided as a convenient
method of completely denying access to a directory, anonymous ftp or
limit block. Because of its precedence, it should not be intermixed with
normal Order/Deny directives. The DenyAll directive can be overridden
at a lower level directory by using AllowAll. DenyAll and AllowAll are
mutually exclusive.See also
AllowAll
Examples
mod_core
DenyFilter
DenyFilter
DenyFilterRegular expression of command arguments to be blockedDenyFilterDefault
None
Context
server config, <VirtualHost>, <Anonymous>, <Global>
Module
mod_core
Compatibility
1.2.0pre7 and later
Description
Similar to AllowFilter, DenyFilter specifies a regular expression
which must not match any of the command arguments. If the regex does
match, a "Forbidden command" error is returned to the client. This can
be especially useful for forbidding certain command argument
combinations from ever reaching ProFTPD.
Notes: The 'PASV' command cannot be blocked using
this directive.
See also
AllowFilter
Examples
# We don't want to allow any commands with % being sent to the server
DenyFilter "%"
mod_core
DenyGroup
DenyGroup
DenyGroupGroup based deny rulesDenyGroupDefault
None
Context
<Limit>
Module
mod_core
Compatibility
1.1.1 and later
Description
DenyGroup specifies a group-expression that is specifically
denied within the context of the
<Limit> block it is applied to. group-expression
has the same format as that used in DefaultRoot,
in that it should contain a comma separated list of groups or "not"
groups (by prefixing a group name with the `!' character) that are to be denied
access to the block. The expression is parsed as a boolean "and" list,
meaning that ALL elements of the expression must evaluate to logically true
in order for the explicit deny to apply.See also
DenyUser,
AllowUser
AllowGroup
Examples
mod_core
DenyUser
DenyUser
DenyUserUser based deny rulesDenyUserDefault
None
Context
<Limit>
Module
mod_core
Compatibility
1.1.7 and later
Description
DenyUser specifies a user-expression that is specifically denied within
the context of the <Limit> block it is applied to. user-expression
is a comma delimited list of users or "not" users (by prefixing
a user name with the `!' character). The expression is parsed as a boolean
"and" list, meaning that all elements of the expression must
evaluate to logically true in order for the explicit deny to apply.See also
DenyGroup,
AllowUser
AllowGroup
Examples
mod_core
Directory
Directory
DirectoryFIXME FIXMEDirectoryDefault
None
Context
server config, <VirtualHost>, <Anonymous>, <Global>
Module
mod_core
Compatibility
0.99.0 and later
Description
This directive creates a block of configuration directives which applies only
to the specified directory and its sub-directories. The block is ended with
</Directory>. Per-directory configuration is enabled during run-time with
a "closest" match algorithm, meaning that the <Directory> directive
with the closest matching path to the actual pathname of the file or directory
in question is used. Per-directory configuration is inherited by all sub-directories
until a closer matching <Directory> is encountered, at which time the
original per-directory configuration is replaced with the closer match. Note
that this does not apply to <Limit> </Limit> blocks, which are
inherited by all sub-directories until a <Limit> block is reached in a
closer match.
Example:
<Directory /users/robroy/private>
HideNoAccess
</Directory>
A trailing slash and wildcard ("/*") can be appended to the directory,
specifying that the configuration block applies only to the contents (and sub-contents),
not to the actual directory itself. Such wildcard matches always take precedence
over non-wildcard <Directory> configuration blocks. <Directory>
blocks cannot be nested (they are automatically nested at run-time based on
their pathnames). Pathnames must always be absolute (except inside
<Anonymous>), and should not reference
symbolic links. Pathnames inside an <Anonymous> block can be relative, indicating
that they are based on the anonymous root directory.
[Notes for ProFTPD 1.1.3 and later only]
Pathnames that begin with the special character '~' and do not specify
a username immediately after ~ are put into a special deferred mode.
When in deferred mode, the directory context is not hashed and sorted into the
configuration tree at boot time, but rather this hashing is deferred until a
user authenticates, at which time the '~' character is replaced with the user's
home directory. This allows a global <Directory> block which applies to
all user's home directories, or sub-directories thereof.
Example:
<Directory ~/anon-ftp>
<Limit WRITE>
DenyAll
</Limit>
</Directory>
See alsoExamples
mod_ls
DirFakeGroup
DirFakeGroup
DirFakeGroupFIXME FIXMEDirFakeGroupDefault
DirFakeGroup Off
Context
server config, <VirtualHost>, <Anonymous>, <Global>
Module
mod_ls
Compatibility
1.1.5
DescriptionDirFakeGroup and its companion directive, DirFakeUser, can be used
to hide the true group and user owners of files in a directory listing.
If simply turned On, DirFakeGroup will display all files as being owned
by group 'ftp'. Optionally, the groupname argument can be used to
specify a specific group other than 'ftp' (an alternate username in the
case of DirFakeUser). "~" can be used as the argument in order to
display the primary group name of the current user (the current user's
username in the case of DirFakeUser).Both DirFakeGroup and DirFakeUser are completely cosmetic; the
groupname or username specified need not exists on the system, and
neither directive affects permissions, real ownership or access control
in any way.See alsoExamples
mod_ls
DirFakeMode
DirFakeMode
DirFakeModeFIXME FIXMEDirFakeModeDefault
None
Context
server config, <VirtualHost>, <Anonymous>, <Directory>, <Global>
Module
mod_ls
Compatibility
1.1.6
Description
The DirFakeMode directive configures a mode (or permissions) which will be
displayed for ALL files and directories in directory listings. For each subset
of permissions (user, group, other), the "execute" permission for directories
is added in listings if the "read" permission is specified by this directive.
For example:
DirFakeMode 0640
Will result in:
-rw-r----- ... arbitrary.file
drwxr-x--- ... arbitrary.directory
As with DirFakeUser, and DirFakeGroup,
the "fake" permissions shown in directory listings are cosmetic only, they do
not affect real permissions or access control in any way.See alsoExamples
mod_ls
DirFakeUser
DirFakeUser
DirFakeUserFIXME FIXMEDirFakeUserDefault
DirFakeUser Off
Context
server config, <VirtualHost>, <Anonymous>, <Global>
Module
mod_ls
Compatibility
1.1.5
Description
See DirFakeGroupSee alsoExamples
mod_code
DisplayConnect
DisplayConnect
DisplayConnectFIXME FIXMEDisplayConnectDefault
None
Context
server config, <VirtualHost>, <Global>
Module
mod_code
Compatibility
1.2.0pre2 and later
Description
The DisplayConnect directive configures an ASCII text filename which
will be displayed to the user when they initially connect but before they
login. The filename can be either relative or absolute. In the case of a
relative filename, the file is searched for starting in the home directory
of the user the server is running as. As this can lead confusion, absolute
pathnames are suggested. If the file cannot be found or accessed, no
error occurs and nothing is logged or displayed to the client.See alsoExamples
mod_code
DisplayFirstChdir
DisplayFirstChdir
DisplayFirstChdirFIXME FIXMEDisplayFirstChdirDefault
None
Context
server config, <VirtualHost>, <Anonymous>, <Directory>, <Global>
Module
mod_code
Compatibility
0.99.0 and later, magic cookies only in 0.99.0pl10
Description
and later
The DisplayFirstChdir directive configures an ASCII text filename which will
be displayed to the user the first time they change into a directory (via CWD)
per a given session. The file will also be displayed if proftpd detects that
its last modification time has changed since the previous CWD into a given
directory. If the filename is relative, it is looked for in the new directory
that the user has changed into. Note that for anonymous ftp logins (see <Anonymous>), the file must
reside inside the chroot()ed file system space. If the file cannot be found
or accessed, no error occurs and nothing is logged or displayed to the client.
DisplayFirstChdir, DisplayConnect, DisplayLogin,
DisplayQuit, support the following "magic cookies"
(only in 0.99.0pl10 and later), which are replaced with their
respective strings before being displayed to the user.
%T
Current Time
%F
Available space on file system
%C
Current working directory
%R
Remote host name
%L
Local host name
%u
Username reported by ident protocol
%U
Username originally used in login
%M
Max number of connections
%N
Current number of connections
%E
Server admin's e-mail address
%x
The name of the user's class
%y
Current number of connections from the user's class
%z
Max number of connections from the user's class
NOTE: not all of these may have a rational value, depending
on the context in which they're used (e.g., %u if ident lookups are off).See alsoExamples
mod_core
DisplayGoAway
DisplayGoAway
DisplayGoAwayFIXME FIXMEDisplayGoAwayDefault
None
Context
server config, <VirtualHost>, <Anonymous>, <Global>
Module
mod_core
Compatibility
1.2.0pre8 and later
Description
The DisplayGoAway directive specifies an ASCII text filename which will be
displayed to the user if the class they're a member of has too many users logged
in and their login request has been denied.
DisplayGoAway supports the same "magic cookies" as DisplayFirstChdir.
See also
DisplayFirstChdir
Examples
mod_core
DisplayLogin
DisplayLogin
DisplayLoginFIXME FIXMEDisplayLoginDefault
None
Context
server config, <VirtualHost>, <Anonymous>, <Global>
Module
mod_core
Compatibility
0.99.0 and later
Description
The DisplayLogin directive configures an ASCII text filename which will be
displayed to the user when they initially login. The filename can be either
relative or absolute. In the case of a relative filename, the file is searched
for in the initial directory a user is placed in immediately after login (home
directory for unix user logins, anonymous-root directory for anonymous logins). Note: that for jailed
logins, the file must reside inside the chroot()ed file system space. If
the file cannot be found or accessed, no error occurs and nothing is logged
or displayed to the client.
DisplayLogin supports the same "magic cookies" as DisplayFirstChdir.
See alsoExamples
mod_core
DisplayQuit
DisplayQuit
DisplayQuitFIXME FIXMEDisplayQuitDefault
None
Context
server config, <VirtualHost>, <Anonymous>, <Global>
Module
mod_core
Compatibility
1.2.0pre8 and later
Description
DisplayQuit configures an ASCII text filename which will be displayed to the
user when they quit. The filename can be either relative or absolute. In the
case of a relative filename, the file is searched for in current directory a
user is in when they logout -- for this reason, a absolute filename is usually
preferable.
NOTE: for jailed logins, the file must reside inside the
chroot()ed file system space. If the file cannot be found or accessed, no error
occurs and nothing is logged or displayed to the client.
DisplayQuit supports the "magic cookies" listed under DisplayFirstChdir.
See alsoExamples
mod_readme
DisplayReadme
DisplayReadme
DisplayReadmeFIXME FIXMEDisplayReadmeDefault
None
Context
server config, <VirtualHost>, <Anonymous>, <Global>
Module
mod_readme
Compatibility
1.2.0pre8 and later
Description
Module: mod_readme
The DisplayReadme directive notifies the user of the last change date of the
specified file or pattern. Only a single DisplayReadme directive is allowed per configuration
scope.
DisplayReadme README
Will result in:
Please read the file README it was last modified on Sun Oct 17 10:36:14
1999 - 0 days ago
Being displayed to the user on a cwd.
DisplayReadmePattern README*
Will result in:
Please read the file README
it was last modified on Tue Jan 25 04:47:48 2000 - 0 days ago
Please read the file README.first
it was last modified on Tue Jan 25 04:48:04 2000 - 0 days ago
Being displayed to the user on a cwd. See alsoExamples
mod_log
ExtendedLog
ExtendedLog
ExtendedLogFIXME FIXMEExtendedLogDefault
None
Context
server config, <VirtualHost>, <Anonymous> <Global>
Module
mod_log
Compatibility
1.1.6pl1 and later
Description
The ExtendedLog directive allows customizable logfiles to be generated, either
globally or per VirtualHost. The filename
argument must contain an absolute pathname to a logfile which will be appended
to when proftpd starts; the pathname should not be to a file in a nonexistent
directory, to a world-writeable directory, or be a symbolic link (unless
AllowLogSymlinks is set to on). Multiple logfiles (potentially with different
command classes and formats) can be created. Optionally, the command-classes
argument can be used to control which types of commands are logged. If not
command classes are specified, proftpd logs all commands by default (passwords
are hidden). command-classes is a comma delimited (no whitespace!) list of
which commands to log.The following are valid classes:
NONE
No commands
AUTH
Authentication commands (USER, PASS)
INFO
Informational commands (PWD, SYST, etc)
DIRS
Directory commands (LIST, CWD, MKD, etc)
READ
File reading (RETR)
WRITE
File/directory writing or creation
MISC
Miscellaneous commands (SITE, etc)
ALL
All commands (default)
If a format-nickname argument is supplied, ExtendedLog
will use the predefined logformat (created by LogFormat).
Otherwise, the default format of "%h %l %u %t \"%r\" %s %b"
is used.
See also
AllowLogSymlinks,
LogFormat,
TransferLog
ExamplesFor example, to log all read and write operations to /var/log/ftp.log (using
the default format), you could:
ExtendedLog /var/log/ftp.log read,write
mod_ratio
FileRatioErrMsg
FileRatioErrMsg
FileRatioErrMsgFIXME FIXMEFileRatioErrMsgDefault
None known
Context
<Directory>, <Anonymous>, <Limit>,.ftpaccess
Module
mod_ratio
Compatibility
at least 1.2.0 and later
Description
The FileRatioErrMsg directive ....
Example:
FileRatioErrMsgSee alsoExamples
mod_sample
FooBarDirective
FooBarDirective
FooBarDirectiveFIXME FIXMEFooBarDirectiveDefault
none
Context
server config, <Anonymous>, <Limit>
Module
mod_sample
Compatibility
at least 1.2.0 and later
Description
FooBarDirective is a dummy directive to be used as a coding
example only.See alsoExamples
mod_core
Global
Global
GlobalFIXME FIXMEGlobalDefault
None
Context
server config, <VirtualHost>
Module
mod_core
Compatibility
1.1.6 and later
Description
The Global configuration block is used to create a set of configuration directives
which is applied universally to both the main server configuration and all VirtualHost
configurations. Most, but not all other directives can be used
inside a Global block.
In addition, multiple <Global> blocks can be created. At runtime, all
Global blocks are merged together and finally into each server's configuration.
Global blocks are terminated by a matching </Global> directive.See alsoExamples
mod_core
Group
Group
GroupFIXME FIXMEGroupDefault
None
Context
server config, <VirtualHost>, <Anonymous>, <Global>
Module
mod_core
Compatibility
0.99.0 and later
Description
The Group directive configures which group the server daemon will normally
run at. See User for more details.See alsoExamples
mod_core
GroupOwner
GroupOwner
GroupOwnerFIXME FIXMEGroupOwnerDefault
None
Context
<Anonymous>, <Directory>, .ftpaccess
Module
mod_core
Compatibility
0.99.0 and later
Description
The GroupOwner directive configures which group all newly created directories
and files will be owned by, within the context that GroupOwner is applied to.
The group ID of groupname cannot be 0.
Note that GroupOwner cannot be used to override the host OS/file system user/group
paradigm. If the current user is not a member of the specified group, new files
and directories will not be able to be chown()ed to the GroupOwner group. If
this happens, file STOR (send file from client to server) and MKD (mkdir) operations
will succeed normally, however the new directory entries will be owned by the
current user's default group (a warning message is also logged) instead of by
the desired group. If you also use UserOwner
in the same context, this restriction is lifted.See alsoExamples
mod_core
GroupPassword
GroupPassword
GroupPasswordFIXME FIXMEGroupPasswordDefault
None
Context
server config, <VirtualHost>, <Anonymous>, <Global>
Module
mod_core
Compatibility
0.99.0pl5 and later
Description
The GroupPassword directive creates a special "group" password which
allows all users in the specified group to authenticate using a single password.
The group/password supplied is only effective inside the context to which GroupPassword
is applied. The hashed-password argument is a standard
cleartext password which has been passed through the standard unix crypt() library
function. Extreme care should be taken when using GroupPassword, as
serious security problems may arise if group membership is not carefully controlled.
See also
UserPassword
Examples
mod_ratio
GroupRatio
GroupRatio
GroupRatioRatio directiveGroupRatioDefault
None known
Context
<Directory>, <Anonymous>, <Limit>,.ftpaccess
Module
mod_ratio
Compatibility
at least 1.2.0 and later
Description
The GroupRatio directive ....
Example:
GroupRatioSee alsoExamples
mod_core
HiddenStor
HiddenStor
HiddenStorEnables more safe file uploadsHiddenStorDefault
HiddenStor off
Context
<Directory>, <Anonymous>, <VirtualHost>, <Global>
Module
mod_core
Compatibility
1.2.0pre5 and later
Description
The HiddenStor directive enables two-step file uploads: files are uploaded
as ".in.filename." and once the upload is complete,
renamed to just "filename". This provides a
degree of atomicity and helps prevent 1) incomplete uploads and 2) files being
used while they're still in the progress of being uploaded. Note:
if the temporary file name is already in use (e.g., a server crash during upload),
it will prevent the file from being uploaded.
The REST (Restart STOR) command is automatically blocked when HiddenStor is
enabled, with the server returning a 501 error code to the client.
See also
AllowStoreRestart
DeleteAbortedStores
Examples
mod_core
HideGroup
HideGroup
HideGroupFIXME FIXMEHideGroupDefault
None
Context
<Directory>, <Anonymous>
Module
mod_core
Compatibility
0.99.0 and later
Description
The HideGroup directive configures a
<Directory> or < Anonymous> block to hide all directory
entries owned by the specified group, unless the group is the primary
group of the currently logged-in, authenticated user . Normally, hidden
directories and files cannot be seen via LIST or NLST commands but can
be operated on via other FTP commands (CWD, DELE, RETR, etc). This behavior
can be modified via the IgnoreHidden directive.See also
See Also: HideUser, HideNoAccess, IgnoreHidden
Examples
mod_core
HideNoAccess
HideNoAccess
HideNoAccessBlock the listing of directory entries to which the user
has no access permissionsHideNoAccessDefault
None
Context
<Directory>,<Anonymous>
Module
mod_core
Compatibility
0.99.0 and later
DescriptionThe HideNoAccess directive configures a <Directory> or
<Anonymous> block to hide all directory entries in a directory
listing (via the LIST or NLST FTP commands) to which the current
logged-in, authenticated user has no access to. Normal Unix-style
permissions always apply, so that although a user may not be able to
see a directory entry that has HideNoAccess applied, they will receive
a normal "Permission denied" error message when attempting
to blindly manipulate the file system object. The directory or file
can be made completely invisible to all FTP commands by applying
IgnoreHidden in conjunction with HideNoAccess.See also
See Also: HideUser, HideGroup, IgnoreHidden
Examples
mod_core
HideUser
HideUser
HideUserFIXME FIXMEHideUserDefault
None
Context
<Directory>, <Anonymous>
Module
mod_core
Compatibility
0.99.0 and later
Description
The HideUser directive configures a <Directory> or <Anonymous>
block to hide all directory entries owned by the specified user, unless
the owning user is the currently logged-in, authenticated user. Normally,
hidden directories and files cannot be seen via LIST or NLST commands but
can be operated on via other FTP commands (CWD, DELE, RETR, etc). This
behavior can be modified via the IgnoreHidden directive. See also
HideGroup, HideNoAccess, IgnoreHidden
Examples
mod_ratio
HostRatio
HostRatio
HostRatioRatio directiveHostRatioDefault
None known
Context
<Directory>, <Anonymous>, <Limit>,.ftpaccess
Module
mod_ratio
Compatibility
at least 1.2.0 and later
Description
The HostRatio directive ....
Example:
HostRatioSee alsoExamples
mod_core
IdentLookups
IdentLookups
IdentLookupsToggle ident lookupsIdentLookupsDefault
IdentLookups on
Context
server config, <VirtualHost>, <Global>
Module
mod_core
Compatibility
1.1.5 and later
Description
Normally, when a client initially connects to proftpd, the ident protocol
(RFC1413) is used to attempt to identify the remote username. This can
be controlled via the IdentLookups directive.See alsoExamples
mod_core
IgnoreHidden
IgnoreHidden
IgnoreHiddenTreat 'hidden' files as if they don't existIgnoreHiddenDefault
IgnoreHidden off
Context
<Limit>
Module
mod_core
Compatibility
0.99.0 and later
Description
Normally, files hidden via HideNoAccess, HideUser or HideGroup
can be operated on by all FTP commands (assuming Unix file
permissions allow access), even though they do not appear in directory
listings. Additionally, even when normal file system permissions disallow
access, proftpd returns a "Permission denied" error to the
client, indicating that the requested object does exist, even if it
cannot be acted upon. IgnoreHidden configures a <Limit> block to
completely ignore any hidden directory entries for the set of limited FTP
commands. This has the effect of returning an error similar to "No
such file or directory" when the client attempts to use the limited
command upon a hidden directory or file.See alsoExamples
mod_core
Include
Include
IncludeLoad additional configuration directives from a fileIncludeDefault
None
Context
server config, <Directory>, <Anonymous>, <VirtualHost>, <Global>
Module
mod_core
Compatibility
1.2.0 and later
Description
This directive allows you to include another configuration file within your current configuration file. The given file argument must be the full path to
the file to be included.See alsoExamples
mod_ldap
LDAPAuthBinds
LDAPAuthBinds
LDAPAuthBindsFIXME FIXMESyntax: LDAPAuthBindsFIX FIX FIXDefault
LDAPAuthBinds off in mod_ldap <= 2.7.6,
LDAPAuthBinds on in mod_ldap >= 2.8
Context
server config, <VirtualHost>, <Global>
Module
mod_ldap
Compatibility
mod_ldap v2.5 and later
DescriptionBy default, the DN specified by LDAPDNInfo will be used to
bind to the LDAP server to obtain user information, including the
userPassword attribute. If LDAPAuthBinds is set to on, the DN
specified by LDAPDNInfo will be used to fetch all user information
except the userPassword attribute. Then, mod_ldap will bind to the
LDAP server as the user who is logging in via FTP with the
user-supplied password. If this bind succeeds, the user is
considered authenticated and is allowed to log in. This method of
LDAP authentication has the added benefit of supporting any password
encryption scheme that your LDAP server supports.See alsoExamples
mod_ldap
LDAPDefaultAuthScheme
LDAPDefaultAuthScheme
LDAPDefaultAuthScheme
Set the authentication scheme/hash that is used when no leading
{hashname} is present.
LDAPDefaultAuthSchemeDefault
LDAPDefaultAuthScheme "crypt"
Context
server config, <VirtualHost>, <Global>
Module
mod_ldap
Compatibility
mod_ldap v2.0 and later
DescriptionSpecifies the authentication scheme used for passwords with no
{prefix} in the LDAP database. For example, if you are using
something like userPassword: mypass in your LDAP database, you would
want to set LDAPDefaultAuthScheme to clear.See alsoExamples
mod_ldap
LDAPDefaultGID
LDAPDefaultGID
LDAPDefaultGID
Set the default GID to be assigned to users when no uidNumber
attribute is found.
LDAPDefaultGIDDefault
None
Context
server config, <VirtualHost>, <Global>
Module
mod_ldap
Compatibility
mod_ldap v2.0 and later
DescriptionThis directive is useful primarily in virtual-user
environments common in large-scale ISPs and hosting organizations.
If a user does not have a LDAP gidNumber attribute, the
LDAPDefaultGID is used. This allows one to have a large number of
users in an LDAP database without gidNumber attributes; setting this
configuration directive will automatically assign those users a
single GID.See alsoExamples
mod_ldap
LDAPDefaultUID
LDAPDefaultUID
LDAPDefaultUID
Set the default GID to be assigned to users when no uidNumber
attribute is found.
LDAPDefaultUIDDefault
None
Context
server config, <VirtualHost>, <Global>
Module
mod_ldap
Compatibility
mod_ldap v2.0 and later
DescriptionThis directive is useful primarily in virtual-user
environments common in large-scale ISPs and hosting organizations.
If a user does not have a LDAP uidNumber attribute, the
LDAPDefaultUID is used. This allows one to have a large number of
users in an LDAP database without uidNumber attributes; setting this
configuration directive will automatically assign those users a
single UID.See alsoExamples
mod_ldap
LDAPDNInfo
LDAPDNInfo
LDAPDNInfoSet DN information to be used for initial bindLDAPDNInfoDefault
LDAPDNInfo "" "" (anonymous bind)
Context
server config, <VirtualHost>, <Global>
Module
mod_ldap
Compatibility
mod_ldap v2.0 and later
DescriptionThis directive specifies the LDAP DN and password to use when
binding to the LDAP server. If this configuration directive is not
specified, anonymous binds are used.See alsoExamples
mod_ldap
LDAPDoAuth
LDAPDoAuth
LDAPDoAuthEnable LDAP authenticationLDAPDoAuthDefault
LDAPDoAuth off
Context
server config, <VirtualHost>, <Global>
Module
mod_ldap
Compatibility
mod_ldap v2.0 and later
DescriptionThis configuration directive activates LDAP authentication.
The second argument to this directive is the LDAP prefix to use for
authentication. The third argument is a template to be used for the
search filter; %u will be replaced with the username that is being
authenticated. By default, the search filter template
"(&(uid=%u)(objectclass=posixAccount))" is used. Search filter
templates are only supported in mod_ldap v2.7 and later.See alsoExamples
mod_ldap
LDAPDoGIDLookups
LDAPDoGIDLookups
LDAPDoGIDLookups
Enable LDAP lookups for user group membership and GIDs in
directory listings
LDAPDoGIDLookupsDefault
LDAPDoGIDLookups off
Context
server config, <VirtualHost>, <Global>
Module
mod_ldap
Compatibility
mod_ldap v2.0 and later
DescriptionThis configuration directive activates LDAP GID-to-name
lookups in directory listings. The second argument to this directive
is the LDAP prefix to use for GID-to-name lookups. The third
argument is a template to be used for the search filter; %u will be
replaced with the GID that is being looked up. By default, the
search filter template
"(&(gidNumber=%u)(objectclass=posixGroup))" is used. Search
filter templates are only supported in mod_ldap v2.7 and
later.See alsoExamples
mod_ldap
LDAPDoUIDLookups
LDAPDoUIDLookups
LDAPDoUIDLookups
Enable LDAP lookups for UIDs in directory listings
LDAPDoUIDLookupsDefault
LDAPDoUIDLookups off
Context
server config, <VirtualHost>, <Global>
Module
mod_ldap
Compatibility
mod_ldap v2.0 and later
DescriptionThis configuration directive activates LDAP UID-to-name
lookups in directory listings. The second argument to this directive
is the LDAP prefix to use for UID-to-name lookups. The third
argument is a template to be used for the search filter; %u will be
replaced with the UID that is being looked up. By default, the
search filter template
"(&(uidNumber=%u)(objectclass=posixAccount))" is used. Search
filter templates are only supported in mod_ldap v2.7 and
later.See alsoExamples
mod_ldap
LDAPForceDefaultGID
LDAPForceDefaultGID
LDAPForceDefaultGIDForce all LDAP-authenticated users to use the same GID.Syntax: LDAPForceDefaultGIDDefault
LDAPForceDefaultGID off
Context
server config, <VirtualHost>, <Global>
Module
mod_ldap
Compatibility
mod_ldap v2.8 and later
DescriptionEven when a LDAPDefaultGID
is configured, mod_ldap will allow individual users to have
gidNumber attributes that will override this default GID. With
LDAPForceDefaultGID enabled, all LDAP-authenticated users are given
the default GID; GIDs may not be overridden by gidNumber
attributes.See alsoExamples
mod_ldap
LDAPForceDefaultUID
LDAPForceDefaultUID
LDAPForceDefaultUIDForce all LDAP-authenticated users to use the same UID.Syntax: LDAPForceDefaultUIDDefault
LDAPForceDefaultUID off
Context
server config, <VirtualHost>, <Global>
Module
mod_ldap
Compatibility
mod_ldap v2.8 and later
DescriptionEven when a LDAPDefaultUID
is configured, mod_ldap will allow individual users to have
uidNumber attributes that will override this default UID. With
LDAPForceDefaultUID enabled, all LDAP-authenticated users are given
the default UID; UIDs may not be overridden by uidNumber
attributes.See alsoExamples
mod_ldap
LDAPHomedirOnDemand
LDAPHomedirOnDemand
LDAPHomedirOnDemand
Enable the creation of user home directories on demand
LDAPHomedirOnDemandDefault
LDAPHomedirOnDemand off
Context
server config, <VirtualHost>, <Global>
Module
mod_ldap
Compatibility
mod_ldap v2.0 and later
DescriptionLDAPHomedirOnDemand activates on-demand home directory creation.
If a user logs in and does not yet have a home directory, a home
directory is created automatically.In mod_ldap <= 2.7.6, the home directory will be owned by the
same user and group that ProFTPD runs as (see the User and Group
configuration directives). mod_ldap >= 2.8 can create home
directories for users with any UID/GID, not just those with the same
UID/GID as the main ProFTPD server.The second argument allows you to specify the mode (default
permissions) to use when creating home directories on demand,
subject to ProFTPD's umask (see the Umask directive). If no
directory mode is specified, the default of 0755 is used. Directory
mode setting is only supported in mod_ldap v2.7 or later.See alsoExamples
mod_ldap
LDAPHomedirOnDemandPrefix
LDAPHomedirOnDemandPrefix
LDAPHomedirOnDemandPrefix
Enable the creation of user home directories on demand
LDAPHomedirOnDemandPrefixDefault
LDAPHomedirOnDemandPrefix off
Context
server config, <VirtualHost>, <Global>
Module
mod_ldap
Compatibility
mod_ldap v2.8 and later
DescriptionLDAPHomedirOnDemandPrefix enables a prefix to be specified for
on-demand home directory creation. This is most useful if mod_ldap
is being used to authenticate against an LDAP directory that does
not return a homeDirectory attribute, either because it cannot
(Microsoft Active Directory, for example) or because you do not wish
to extend your existing directory schema.For example, setting this directive to "/home" and logging in
as the user "joe" would result in his home directory being created
as "/home/joe". The directory will be created with the mode
specified in LDAPHomedirOnDemand. To use
this directive, LDAPHomedirOnDemand must be
enabled.See alsoExamples
mod_ldap
LDAPHomedirOnDemandPrefixNoUsername
LDAPHomedirOnDemandPrefixNoUsername
LDAPHomedirOnDemandPrefixNoUsernameFIXFIXFIXLDAPHomedirOnDemandPrefixNoUsernameDefault
FIXFIXFIX
Context
server config, <Global>, <VirtualHost>, <Anonymous>, <Limit>, .ftpaccess
Module
mod_ldap
Compatibility
1.2.5rc1 and later
Description
FIX FIX FIX
See alsoExamples
FIXFIXFIX
FIXFIX
mod_ldap
LDAPHomedirOnDemandSuffix
LDAPHomedirOnDemandSuffix
LDAPHomedirOnDemandSuffix
Specify an additional directory to be created inside a user's
home directory on demand.
LDAPHomedirOnDemandSuffixDefault
LDAPHomedirOnDemandSuffix ""
Context
server config, <VirtualHost>, <Global>
Module
mod_ldap
Compatibility
mod_ldap v2.6 and later.
Descriptionto be created within a user's home directory when it is
created on demand. For example, if a user's home directory is
"/home/user", setting this configuration directive to "public_html"
will also create "/home/user/public_html" on demand. In mod_ldap
v2.7.6 and earlier, you must also activate LDAPHomedirOnDemand in
your configuration.mod_ldap >= 2.8 supports multiple suffix arguments and does
not require LDAPHomedirOnDemand to be enabled.See alsoExamples
mod_ldap
LDAPNegativeCache
LDAPNegativeCache
LDAPNegativeCacheEnable negative caching for LDAP lookupsLDAPNegativeCacheDefault
LDAPNegativeCache off
Context
server config, <VirtualHost>, <Global>
Module
mod_ldap
Compatibility
mod_ldap v1.1 and later
DescriptionLDAPNegativeCache specifies whether or not to cache negative
responses from the LDAP server when using LDAP for UID/GID lookups.
This option is useful if you also use/are in transition from another
authentication system; if there are many users in your old
authentication system that aren't in the LDAP database, there can be
a significant delay when a directory listing is performed as the
UIDs not in the LDAP database are repeatedly looked up in an attempt
to present usernames instead of UIDs in directory listings. With
LDAPNegativeCache set to on, negative ("not found") responses from
the LDAP server will be cached and speed will improve on directory
listings that contain many users not present in the LDAP
database.See alsoExamples
mod_ldap
LDAPQueryTimeout
LDAPQueryTimeout
LDAPQueryTimeoutSet a timeout for LDAP queriesLDAPQueryTimeoutDefault
LDAPQueryTimeout default-api-timeout
Context
server config, <VirtualHost>, <Global>
Module
mod_ldap
Compatibility
mod_ldap v2.0 and later
DescriptionSets the timeout used for LDAP directory queries. The default
is the default timeout used by your LDAP API.See alsoExamples
mod_ldap
LDAPSearchScope
LDAPSearchScope
LDAPSearchScopeSpecify the search scope used in LDAP queriesLDAPSearchScopeDefault
LDAPSearchScope subtree
Context
server config, <VirtualHost>, <Global>
Module
mod_ldap
Compatibility
mod_ldap v2.6 and later
DescriptionSet the scope used for LDAP searches. The default setting,
subtree, searches for all entries in the tree from the current level
down. Setting this directive to onelevel searches only one level
deep in the LDAP tree.See alsoExamples
mod_ldap
LDAPServer
LDAPServer
LDAPServerSpecify the LDAP server to use for lookupsLDAPServerDefault
LDAPServer "localhost"
Context
server config, <VirtualHost>, <Global>
Module
mod_ldap
Compatibility
mod_ldap v1.0 and later
DescriptionLDAPServer allows you to to specify the hostname(s) and
port(s) of the LDAP server(s) to use for LDAP authentication. If no
LDAPServer configuration directive is present, the default LDAP
servers specified by your LDAP API will be used.See alsoExamples
mod_ldap
LDAPUseTLS
LDAPUseTLS
LDAPUseTLSEnable TLS/SSL connections to the LDAP server.Syntax: LDAPUseTLSDefault
LDAPUseTLS off
Context
server config, <VirtualHost>, <Global>
Module
mod_ldap
Compatibility
mod_ldap v2.8 and later
DescriptionBy default, mod_ldap connects to the LDAP server via a
non-encrypted connection. Enabling this option causes mod_ldap to
use an encrypted (TLS/SSL) connection to the LDAP server. If a
secure connection to the LDAP server fails, mod_ldap will not
authenticate users (mod_ldap will *not* fall back to an unsecure
connection).See alsoExamples
mod_ratio
LeechRatioMsg
LeechRatioMsg
LeechRatioMsgSets the 'over ratio' error messageLeechRatioMsgDefault
None known
Context
<Directory>, <Anonymous>, <Limit>,.ftpaccess
Module
mod_ratio
Compatibility
at least 1.2.0 and later
Description
The LeechRatioMsg directive defines the response message sent
back to the client upon breaking their quota limits.See alsoExamples
LeechRatioMsg "please upload as well as download"
mod_core
Limit
Limit
LimitFIXME FIXMELimitDefault
None
Context
server config, <VirtualHost>, <Directory>, <Anonymous>, <Global>, .ftpaccess
Module
mod_core
Compatibility
0.99.0 and later
Description
The Limit configuration block is used to place access restrictions on one or
more FTP commands, within a given context. Limits flow downward, so that a Limit
configuration in the server config context applies to all <Directory>
and <Anonymous> blocks that also
reside in the configuration; until it is overridden by a "lower" <Limit>
block. Any number of command parameters can be specified,
against which the contents of the <Limit> block will be applied. command
can be any valid FTP command, but is generally one of the following:
CWD (Change Working Directory)
Sent by client when changing directories.
MKD (MaKe Directory)
Sent by client to create a new directory.
RNFR (ReName FRom), RNTO (ReName TO)
Sent as a pair by client to rename a directory entry.
DELE (DELEte)
Sent by client to delete a file.
RMD (ReMove Directory)
Sent by client to remove a directory.
RETR (RETRieve)
Transfer a file from the server to the client.
STOR (STORe)
Transfer a file from the client to the server.
In addition, the following command-groups are accepted.
They have a lower precedence than real commands, meaning that a real command
limit will always be applied instead of the command-group.
READ
All FTP commands which deal with file reading (directory listing not included):
RETR, SITE, SIZE, STAT
WRITE
All FTP commands which deal with file or directory write/creation/deletion:
APPE, DELE, MKD, RMD, RNTO, STOR, XMKD, XRMD
DIRS
All FTP commands which deal with directory listing:
CDUP, CWD, LIST, MDTM, NLST, PWD, RNFR, XCUP, XCWD, XPWD
ALL
ALL FTP commands (identical to READ WRITE DIRS). Note this group has the
lowest precedence of all; it will not override a limit imposed by another
command-group (e.g. DIRS).
Finally, a special command is allowed which can be used to control login access:
LOGIN
Connection or login to the server. Applying a <Limit> to this pseudo-command
can be used to allow or deny initial connection or login to the context. It
has no effect, and is ignored, when used in a context other than server config,
<VirtualHost> or <Anonymous>
(i.e. using it in a <Directory> context is
meaningless).
<Limit> command restrictions should not be confused with file/directory
access permission. While limits can be used to restrict a command on a certain
directory, they cannot be used to override the file permissions inherent to
the base operating/file system.
The following FTP commands cannot be restricted via <Limit>:
ABOR
HELP
MODE (not implemented, always S)
NOOP
PASS (use <Limit LOGIN>)
PASV
PORT
QUIT
REST (use AllowRetrieveRestart, AllowStoreRestart)
STRU (not implemented, always F)
SYST
TYPE
USER (use <Limit LOGIN>)
See also
See Also: IgnoreHidden
Examples
mod_log
LogFormat
LogFormat
LogFormatSpecify a logging formatLogFormatDefault
LogFormat default "%h %l %u %t \"%r\" %s %b"
Context
server config
Module
mod_log
Compatibility
1.1.6pl1 and later
Description
The LogFormat directive can be used to create a custom logging format for use
with the ExtendedLog directive. Once created, the
format can be referenced by the specified nickname.
The format-string argument can consist of any combination
of letters, numbers and symbols. The special character % is
used to start a meta-sequence (see below). To insert a literal % character,
use %%.
The following meta sequences are available and are replaced as indicated
when logging.
%A
Anonymous username (password given), or UNKNOWN if non-anonymous
%b
Bytes sent for request
%f
Filename stored or retrieved, absolute path (not chrooted)
%F
Filename stored or retrieved, as the client sees it
%{FOOBAR}e
Contents of environment variable FOOBAR. Note that the server does not set
any environment variables itself.
%h
Remote host name
%a
Remote IP address
%l
Remote username (from ident), or UNKNOWN if ident lookup failed
%m
Command (method) name received from client, e.g., RETR
%p
Local server port number
%v
Local server name
%P
Local server process id (pid)
%r
Full command line received from client
%t
Current local time
%{format}t
Current local time formatted (strftime(3) format)
%T
Time taken to transmit/receive file, in seconds
%s
Numeric FTP response code (status)
%u
Local authenticated userid
See also
ExtendedLog,
TransferLog
Examples
mod_auth
LoginPasswordPrompt
LoginPasswordPrompt
LoginPasswordPromptFIXME FIXMELoginPasswordPromptDefault
LoginPasswordPrompt on
Context
server config, <VirtualHost>, <Anonymous>, <Global>
Module
mod_auth
Compatibility
1.2.0pre1 and later
Description
If set to off, ProFTPd will skip the password request if the
login will be denied regardless of password, e.g., if a <Limit LOGIN>
directive forbids the connection.See alsoExamples
mod_ls
LsDefaultOptions
LsDefaultOptions
LsDefaultOptionsFIXME FIXMELsDefaultOptionsDefault
None
Context
server config, <VirtualHost>, <Anonymous>, <Global>
Module
mod_ls
Compatibility
1.1.6 and later
Description
Normally, FTP commands involving directory listings (NLST, LIST and STAT)
use the arguments (options) passed by the client to determine what files are
displayed and the format they are displayed in. Using the LsDefaultOptions
directive can alter the default behavior of such listings, but implying that
a certain option (or options) is always present. For example, to force all
directory listings to always display ".dotfiles", one might:
LsDefaultOptions "-a"See alsoExamples
mod_core
MasqueradeAddress
MasqueradeAddress
MasqueradeAddressConfigure the server address presented to clientsMasqueradeAddressDefault
none
Context
server config, <VirtualHost>
Module
mod_core
Compatibility
1.2.2 and later
Description
MasqueradeAddress causes the server to display the network information for
the specified IP address or DNS hostname to the client, on the assumption
that that IP address or DNS host is acting as a NAT gateway or port forwarder
for the server.
See alsoExamples
MasqueradeAddress nat-gw.mydomain.com
mod_core
MaxClients
MaxClients
MaxClientsLimits the number of users that can connectMaxClientsDefault
MaxClients none
Context
server config, <Anonymous>, <VirtualHost>, <Global>
Module
mod_core
Compatibility
0.99.0 and later
Description
The MaxClients directive configures the maximum number of authenticated clients
which may be logged into a server or anonymous account. Once this limit is
reached, additional clients attempting to authenticate will be disconnected.
The special value none may be supplied which removes
all maximum connection limits from the applicable configuration context. Additionally,
an optional message argument may be used which will
be displayed to a client attempting to exceed the maximum value; immediately
before disconnection. The message argument is parsed
for the magic string "%m", which is replaced with
the configured maximum value. If message is not
supplied, a system-wide default message is used.
Example:
MaxClients 5 "Sorry, the maximum number of allowed users are already
connected (%m)"
Results in:
530 Sorry, the maximum number of allowed users are already connected
(5)See alsoExamples
mod_core
MaxClientsPerHost
MaxClientsPerHost
MaxClientsPerHostLimits the connections per client machineMaxClientsPerHostDefault
MaxClientsPerHost none
Context
server config, <Anonymous>, <VirtualHost>, <Global>
Module
mod_core
Compatibility
1.1.7 and later
Description
The MaxClientsPerHost directive configures the maximum number of clients
allowed to connect per host. The optional argument message
may be used which will be displayed to a client attempting to exceed the maximum
value. If message is not supplied, a default message of
"Sorry, the maximum number clients (%m) from your host are already connected."
is used. See also
MaxClients, MaxHostsPerUser
Examples
MaxClientsPerHost 1 "Sorry, you may not connect more than one time."
Results in: 530 Sorry, you may not connect more than one time.
mod_core
MaxHostsPerUser
MaxHostsPerUser
MaxHostsPerUserLimit the number of connections per useridMaxHostsPerUserDefault
MaxHostsPerUser none
Context
server config, <Anonymous>, <VirtualHost>, <Global>
Module
mod_core
Compatibility
1.2.4 and later
Description
The MaxHostsPerUser directive configures the maximum number of times
any given login can connection at any given time. The optional argument
message may be used which will be displayed to a client attempting
to exceed the maximum value. If message is not supplied, a default
message of "Sorry, the maximum number of hosts (%m) for this user
already connected."See also
MaxClients,
MaxClientsPerHost
Examples
MaxHostsPerUser 1 "Sorry, you may not connect more than one time."
Results in: 530 Sorry, you may not connect more than one time.
mod_core
MaxInstances
MaxInstances
MaxInstancesSets the maximum number of child processes to be spawnedMaxInstancesDefault
MaxInstances none
Context
server config
Module
mod_core
Compatibility
1.1.6pl1
Description
The MaxInstances directive configures the maximum number of child processes
that may be spawned by a parent proftpd process in standalone
mode. The directive has no effect when used on a server running in inetd
mode.
Because each child proftpd process represents a single client connection,
this directive also controls the maximum number of simultaneous connections
allowed. Additional connections beyond the configured limit are syslog'd and
silently disconnected. The MaxInstances directive can be used to prevent undesirable
denial-of-service attacks (repeatedly connecting to the ftp port, causing
proftpd to fork-bomb). By default, no limit is placed on the number of child
processes that may run at one time.See alsoExamples
mod_core
MaxLoginAttempts
MaxLoginAttempts
MaxLoginAttemptsSets how many password attempts are allowed before disconnectionMaxLoginAttemptsDefault
MaxLoginAttempts 3
Context
server config, <VirtualHost>, <Global>
Module
mod_core
Compatibility
0.99.0 and later
Description
The MaxLoginAttempts directive configures the maximum number of times a client
may attempt to authenticate to the server during a given connection. After
the number of attempts exceeds this value, the user is disconnected and an
appropriate message is logged via the syslog mechanism.See alsoExamples
mod_core
MultilineRFC2228
MultilineRFC2228
MultilineRFC2228FIXME FIXMEMultilineRFC2228Default
MultilineRFC2228 off
Context
server config
Module
mod_core
Compatibility
1.2.0pre3 and later
Description
By default, proftpd sends multiline responses as per RFC 959, i.e.:
200-First line
More lines...
200 Last line
RFC 2228 specifies that "6xy"
response codes will be sent as follows:
600-First line
600-More lines...
600 Last line
Note that 2228 ONLY specifies this for response codes starting with
'6'. Enabling this directive causes ALL responses to be sent in this
format, which may be more compatible with certain web browsers and clients.
Also note that this is NOT the same as wu-ftpd's multiline responses,
which do not comply with any RFC. Using this method of multilines is more likely
to be compatible with all clients, although it isn't strictly RFC, and is thus
not enabled by default.See alsoExamples
mod_sql
MySQLInfo
MySQLInfo
MySQLInfoConfigures the MySQL driverMySQLInfoDefault
none
Context
server config, <Global>, <VirtualHost>
Module
mod_sql
Compatibility
1.2.0rc2 and later
DescriptionThis directive is deprecated as of 1.2.0. Please use
SQLConnectInfo instead.Configures the MySQL database driver (the database may be
remote). A connection isn't made until use of a SQL feature requires
it, after which it may be held open for the lifetime of the FTP
session depending on the directives in use. Use `""' to specify a
null password.See alsoExamples
mod_core
Order
Order
OrderConfigures the precedence of the Limit directivesOrderDefault
Order allow,deny
Context
<Limit>
Module
mod_core
Compatibility
0.99.0pl6 and later
Description
The Order directive configures the order in which Allow and Deny directives are checked inside of a <Limit> block. Because Allow directives are permissive, and Deny directives restrictive, the order in which they are examined can significantly alter the way security functions. If the default setting of allow,deny is used, "allowed" access permissions are checked first. If an Allow directive explicitly allows access to the <Limit> context, access is granted and any Deny directives are never checked. If Allow did not explicitly permit access, Deny directives are checked. If any Deny directive applies, access is explicitly denied. Otherwise, access is granted. When deny,allow is used, "deny" access
restrictions are checked first. If any restriction applies, access is denied
immediately. If nothing is denied, Allow permissions
are checked. If an Allow explicitly permits access, access
to the entire context is permitted; otherwise access is implicitly denied.
For clarification, the following illustrates the steps used when checking
Allow/Deny access:
Order allow,deny
Check Allow directives. If one or more apply, exit with result: ALLOW
Check Deny directives. If one or more apply, exit with result: DENY
Exit with default implicit ALLOW
Order deny,allow
Check Deny directives. If one or more apply, exit with result: DENY
Check Allow directives. If one or more apply, exit with result: ALLOW
Exit with default implicit: DENYSee alsoExamples
mod_core
PassivePorts
PassivePorts
PassivePortsSpecify the ftp-data port range to be usedPassivePortsDefault
None
Context
server config, <VirtualHost>, <Global>
Module
mod_core
Compatibility
1.2.0rc2 and later
DescriptionPassivePorts restricts the range of ports from which the server
will select when sent the PASV command from a client. The server will
randomly choose a number from within the specified range until an open
port is found. Should no open ports be found within the given range,
the server will default to a normal kernel-assigned port, and a
message logged.The port range selected must be in the non-privileged range
(eg. greater than or equal to 1024); it is STRONGLY
RECOMMENDED that the chosen range be large enough to handle many
simultaneous passive connections (for example, 49152-65534, the
IANA-registered ephemeral port range).See alsoExamples
# Use the IANA registered ephemeral port range
PassivePorts 49152 65534
mod_core
PathAllowFilter
PathAllowFilter
PathAllowFilterFIXME FIXMEPathAllowFilterDefault
None
Context
server config, <VirtualHost>, <Anonymous>, <Global>
Module
mod_core
Compatibility
1.1.7 and later
Description
PathAllowFilter allows the configuration of a regular expression that must
be matched for all newly uploaded (stored) files. The regular expression is
applied against the entire pathname specified by the client, so care must
be taken when creating a proper regex. Paths that fail the regex match result
in a "Forbidden filename" error being returned to the client.
If the regular-expression argument contains whitespace,
it must be enclosed in quotes.See alsoExamples
# Only allow a-z 0-9 . - _ in file names,
PathAllowFilter ^[a-z0-9._-]+$
# as above but with upper case characters as well
PathAllowFilter ^[A-Za-z0-9._-]+$
mod_core
PathDenyFilter
PathDenyFilter
PathDenyFilterFIXME FIXMEPathDenyFilterDefault
None
Context
server config, <VirtualHost>, <Anonymous>, <Global>
Module
mod_core
Compatibility
1.1.7 and later
Description
Similar to PathAllowFilter, PathDenyFilter
specifies a regular expression which must not match any uploaded
pathnames. If the regex does match, a "Forbidden filename" error is returned
to the client. This can be especially useful for forbidding .ftpaccess or
.htaccess files.See alsoExamples
# We don't want .ftpaccess or .htaccess files to be uploaded
PathDenyFilter "(\\.ftpaccess)|(\\.htaccess)$"
mod_unixpw
PersistentPasswd
PersistentPasswd
PersistentPasswdFIXME FIXMEPersistentPasswdDefault
Platform dependent
Context
server config
Module
mod_unixpw
Compatibility
1.1.5 and later
Description
The PersistentPasswd directive controls how proftpd handles authentication,
user/group lookups, and user/group to name mapping. If set to On, proftpd
will attempt to open the system-wide /etc/passwd, /etc/group (and /etc/shadow,
potentially) files itself, holding them open even during a chroot()ed login
(note that /etc/shadow is never held open, for security reasons). On some
platforms, you must turn this option on, as the libc functions are incapable
of accessing these databases from inside of a chroot(). At configure-time,
the configuration script will attempt to detect whether or not you need this
support, and make it the default. However, such "guessing" may fail,
and you will have to manually enable or disable the feature. If you cannot
see user or group names when performing a directory listing inside an anonymous
chrooted login, this indicates you must enable the directive. Use of the AuthUserFile
or
AuthGroupFile directives will force partial support
for persistent user or group database files; regardless of PersistentPasswd's
setting.
Note: NIS or NIS+ users will most likely want to disable this feature,
regardless of proftpd's detected configuration defaults. Failure to disable
this will make your NIS/NIS+ maps not work! On certain systems, you may also
need to compile ProFTPD with the --enable-autoshadow option in order to
authenticate both users from NIS maps and local users.See alsoExamples
mod_core
PidFile
PidFile
PidFileFIXME FIXMEPidFileDefault
none
Context
server config, <Global>
Module
mod_core
Compatibility
1.2.0rc2 and later
Description
The PidFile directive sets the file to which the server records
the process id of the daemon. The filename should be relative to the
system root, ie /var/run/proftpd/pidfile. The PidFile is only used
in standalone mode.
It is often useful to be able to send the server a signal, so
that it closes and then reopens its ErrorLog and TransferLog, and
re-reads its configuration files. This is done by sending a SIGHUP
(kill -1) signal to the process id of the master daemon listed in
the PidFile.See alsoExamples
mod_core
Port
Port
PortFIXME FIXMEPortDefault
Port 21
Context
server config, <VirtualHost>
Module
mod_core
Compatibility
0.99.0 and later
Description
The Port directive configures the TCP port which proftpd will listen on while
running in standalone mode. It has no effect when used upon a server running in
inetd mode (see ServerType). The directive can be used in conjunction with
<VirtualHost> in order to run a virtual server on the same IP address
as the master server, but listening on a different port.
For any server, either <VirtualHost> or server config, setting
Port 0 effectively turns off that server.
See alsoExamples
mod_sql
PostgresInfo
PostgresInfo
PostgresInfoPostgres backend configuration (Deprecated)PostgresInfoDefault
none
Context
server config, <Global>, <VirtualHost>
Module
mod_sql
Compatibility
1.2.0rc2 and later
DescriptionThis directive is deprecated, please use SQLConnectInfo
instead.Configures the Posgresql database driver (the database may be
remote). A connection isn't made until use of a SQL feature requires
it, after which it may be held open for the lifetime of the FTP
session depending on the directives in use.See alsoExamples
PostgresInfo myserver.example.com proftpd wibble ftpusers
mod_sql
PostgresPort
PostgresPort
PostgresPortSets the port postgres is listening onPostgresPortDefault
5432
Context
server config, <Global>, <VirtualHost>
Module
mod_sql
Compatibility
1.2.0rc2 and later
DescriptionThis directive is deprecated, please use SQLConnectInfo
instead
Specifies which TCP/IP port to use for connecting. Default is 5432,
or UNIX socket for localhost.
See alsoExamples
PostgresPort 3306
mod_quota
QuotaBlockName
QuotaBlockName
QuotaBlockNameFIXME FIXMEQuotaBlockNameDefault
byte
Context
server, <VirtualHost>, <Anonymous>
Module
mod_quota
Compatibility
at least 1.2.0 and later
Description
The QuotaBlockName directive is used in conjunction with the QuotaBlockSize directive to control user
output from the module. This directive specifies the name given to
the values displayed (ie byte, kilobyte, kb etc etc).
Example:
QuotaBlockName kbSee alsoExamples
mod_quota
QuotaBlockSize
QuotaBlockSize
QuotaBlockSizeFIXME FIXMEQuotaBlockSizeDefault
None
Context
server, <VirtualHost>, <Anonymous>
Module
mod_quota
Compatibility
at least 1.2.0 and later
Description
The QuotaBlockSize directive is used in conjuntion with the QuotaBlockName directive to control how
the user output is handled. QuotaBlockSize specifies the factor by
which the values in the user reports are divided before display.
Example:
QuotaBlockSize 1024See alsoExamples
mod_quota
QuotaCalc
QuotaCalc
QuotaCalcFIXME FIXMEQuotaCalcDefault
None
Context
server, <VirtualHost>, <Anonymous>
Module
mod_quota
Compatibility
at least 1.2.0 and later
Description
The QuotaCalc directive controls whether calculation is done on
the fly. If the directive is set to 'on' and either there is no
.quota file or the quota would go negative then calculation is done
on the fly rather than at the end of the session.See alsoExamples
mod_quota
QuotaExempt
QuotaExempt
QuotaExemptFIXME FIXMEQuotaExemptDefault
None
Context
server, <VirtualHost>, <Anonymous>
Module
mod_quota
Compatibility
at least 1.2.0 and later
Description
The QuotaExempt directive lists the UIDs which are not subject to
quota controls, using UIDs rather than symbolic user names speeds up
the loading and resolution process.
Example:
QuotaExempt 3000,3401,500See alsoExamples
mod_quota
Quotas
Quotas
QuotasFIXME FIXMEQuotasDefault
none
Context
server, <VirtualHost>, <Anonymous>
Module
mod_quota
Compatibility
at least 1.2.0 and later
Description
The Quotas directive enables or disables Quota support.
Example:
Quotas onSee alsoExamples
mod_quota
QuotaType
QuotaType
QuotaTypeFIXME FIXMEQuotaTypeDefault
soft
Context
server, <VirtualHost>, <Anonymous>
Module
mod_quota
Compatibility
at least 1.2.0 and later
Description
The QuotaType directive defines what happens to files which break
the quota limits as they are uploaded. Setting the type to hard
ensures that the file which violates the quota is deleted.
uploaded.See alsoExamples
mod_xfer
RateReadBPS
RateReadBPS
RateReadBPSFIXME FIXMERateReadBPSDefault
0
Context
server config, <VirtualHost>, <Anonymous>, <Directory>, <Global>
Module
mod_xfer
Compatibility
1.2.0 and later
Description
RateReadBPS sets the allowed byte per second download bandwidth in the given
config context. Zero means no bandwidth limit. (See RateReadFreeBytes
about limiting bandwidth only after some amount of downloaded bytes.) The
usual place for this directive is in <VirtualHost> or <Directory> sections. See alsoExamples
mod_xfer
RateReadFreeBytes
RateReadFreeBytes
RateReadFreeBytesFIXME FIXMERateReadFreeBytesDefault
0
Context
server config, <VirtualHost>, <Anonymous>, <Directory>, <Global>
Module
mod_xfer
Compatibility
1.2.0 and later
Description
RateReadFreeBytes is the amount of bytes to be transferred without any bandwidth
limits, so with that option you can give full bandwidth for small files
while limiting big ones. (See RateReadHardBPS
on further info about what happens after the free amount was transferred.) See alsoExamples
mod_xfer
RateReadHardBPS
RateReadHardBPS
RateReadHardBPSFIXME FIXMERateReadHardBPSDefault
off
Context
server config, <VirtualHost>, <Anonymous>, <Directory>, <Global>
Module
mod_xfer
Compatibility
1.2.0 and later
Description
RateReadHardBPS forces the bandwidth to the given RateReadBPS
value after the RateReadFreeBytes amount
of file was transfered. This means that if the user have huge bandwidth and
downloaded the "free" amount fast, HardBPS will stop the transfer until the
average goes down to the given limit. If the amount of FreeBytes is high and
the ReadBPS is low then the user may wait for extended periods of time until
the transfer continues. :-)See alsoExamples
mod_xfer
RateWriteBPS
RateWriteBPS
RateWriteBPSFIXME FIXMERateWriteBPSDefault
0
Context
server config, <VirtualHost>, <Anonymous>, <Directory>, <Global>
Module
mod_xfer
Compatibility
1.2.0 and later
Description
RateWriteBPS sets the allowed byte per second upload bandwidth
in the given config context. Zero means no bandwidth limit. (See
RateWriteFreeBytes about limiting bandwidth only after some amount
of uploaded bytes.) The usual place for this directive is in
<VirtualHost> or <Directory> sections.See alsoExamples
mod_xfer
RateWriteFreeBytes
RateWriteFreeBytes
RateWriteFreeBytesFIXME FIXMERateWriteFreeBytesDefault
0
Context
server config, <VirtualHost>, <Anonymous>, <Directory>, <Global>
Module
mod_xfer
Compatibility
1.2.0 and later
Description
RateWriteFreeBytes is the amount of bytes to be transferred without any bandwidth
limits, so with that option you can give full bandwidth for small files
while limiting big ones. (See RateWriteHardBPS
on further info about what happens after the free amount was transferred.) See alsoExamples
mod_xfer
RateWriteHardBPS
RateWriteHardBPS
RateWriteHardBPSFIXME FIXMERateWriteHardBPSDefault
off
Context
server config, <VirtualHost>, <Anonymous>, <Directory>, <Global>
Module
mod_xfer
Compatibility
1.2.0 and later
Description
RateWriteHardBPS forces the bandwidth to the given RateWriteBPS
value after the RateWriteFreeBytes amount
of file was transfered. This means that if the user have huge bandwidth and
uploaded the "free" amount fast, HardBPS will stop the transfer until the
average goes down to the given limit. If the amount of FreeBytes is high and
the WriteBPS is low then the user may wait for extended periods of time until
the transfer continues. :-)
RateWriteHardBPS
RatioFile (mod_ratio) Incomplete
Ratios (mod_ratio) Incomplete
RatioTempFile (mod_ratio) IncompleteSee alsoExamples
mod_ratio
RatioFile
RatioFile
RatioFileRatio directiveRatioFileDefault
None known
Context
<Directory>, <Anonymous>, <Limit>,.ftpaccess
Module
mod_ratio
Compatibility
at least 1.2.0 and later
Description
The RatioFile directive ....
Example:
RatioFileSee alsoExamples
mod_ratio
Ratios
Ratios
RatiosFIXME FIXMERatiosDefault
None known
Context
<Directory>, <Anonymous>, <Limit>,.ftpaccess
Module
mod_ratio
Compatibility
at least 1.2.0 and later
Description
The Ratios directive ....
Example:
RatiosSee alsoExamples
mod_ratio
RatioTempFile
RatioTempFile
RatioTempFileRatio directiveRatioTempFileDefault
None known
Context
<Directory>, <Anonymous>, <Limit>,.ftpaccess
Module
mod_ratio
Compatibility
at least 1.2.0 and later
Description
The RatioTempFile directive ....
Example:
RatioTempFileSee alsoExamples
mod_core
RequireValidShell
RequireValidShell
RequireValidShellAllow connections based on /etc/shellsRequireValidShellDefault
RequireValidShell on
Context
server config, <VirtualHost>, <Anonymous>, <Global>
Module
mod_core
Compatibility
0.99.0 and later
Description
The RequireValidShell directive configures the server, virtual host or anonymous
login to allow or deny logins which do not have a shell binary listed in /etc/shells.
By default, proftpd disallows logins if the user's default shell is not listed
in /etc/shells. If /etc/shells cannot be found, all default shells are assumed
to be valid.See alsoExamples
mod_core
RLimitCPU
RLimitCPU
RLimitCPUConfigure the maximum CPU time in seconds used by a processRLimitCPUDefault
System defaults
Context
server config
Module
mod_core
Compatibility
1.2.1rc1 and later
Description
RLimitCPU takes 1 or 2 parameters. The first parameter sets the soft resource
limit for all proftpd processes. The optional second parameter sets the
maximum resource limit. Either parameter can be a number, or max to
indicate to the server that the limit should be set to the maximum allowed
by the operating system configuration.
CPU resource limits are expressed in seconds per process.
See also
RLimitMemory,
RLimitOpenFiles
Examples
mod_core
RLimitMemory
RLimitMemory
RLimitMemoryConfigure the maximum memory in bytes used by a processRLimitMemoryDefault
None
Context
server config
Module
mod_core
Compatibility
1.2.1rc1 and later
Description
RLimitMemory takes 1 or 2 parameters. The first parameter sets the soft resource
limit for all proftpd processes. The optional second parameter sets the
maximum resource limit. Either parameter can be a number, or max to
indicate to the server that the limit should be set to the maximum allowed
by the operating system configuration.
Memory resource limits are expressed in bytes per process. An optional
case-insensitive units specifier may follow the number of bytes given:
G (Gigabytes), M (Megabytes), K (Kilobytes), or B (bytes). If the units
specifier is used, the given number of bytes is multiplied by the appropriate
factor.
See also
RLimitCPU, RLimitMaxProcesses, RLimitOpenFiles
mod_core
RLimitOpenFiles
RLimitOpenFiles
RLimitOpenFilesConfigure the maximum number of open files used by a processRLimitOpenFilesDefault
None
Context
server config
Module
mod_core
Compatibility
1.2.1rc1 and later
Description
RLimitOpenFiles takes 1 or 2 parameters. The first parameter sets the soft
resource limit for all proftpd processes. The optional second parameter sets
the maximum resource limit. Either parameter can be a number, or max to
indicate to the server that the limit should be set to the maximum allowed
by the operating system configuration.
File resource limits are expressed in number of files per process.
See also
RLimitCPU, RLimitMaxProcesses, RLimitMemory
mod_auth
RootLogin
RootLogin
RootLoginPermit root user loginsRootLoginDefault
RootLogin off
Context
server config, <VirtualHost>, <Anonymous>, <Global>
Module
mod_auth
Compatibility
1.1.5 and later
Description
Normally, proftpd disallows root logins under any circumstance. If a client
attempts to login as root, using the correct password, a special security
message is sent to syslog. When the RootLogin directive is turned On, the
root user may authenticate just as any other user could (assuming no other
access control measures deny access); however the root login security message
is still sysloged. Obviously, extreme
care should be taken when using this directive.
The use of RootLogin in the Anonymous context is only valid when the User / Group defined in the Anonymous block is set to 'root'
See alsoExamples
mod_ratio
SaveRatios
SaveRatios
SaveRatiosFIXME FIXMESaveRatiosDefault
None known
Context
<Directory>, <Anonymous>, <Limit>,.ftpaccess
Module
mod_ratio
Compatibility
at least 1.2.0 and later
Description
The SaveRatios directive ....
Example:
SaveRatiosSee alsoExamples
mod_core
ScoreboardPath
ScoreboardPath
ScoreboardPathSets the path to the scoreboard fileScoreboardPathDefault
ScoreboardPath /var/run
Context
server config
Module
mod_core
Compatibility
1.1.6 and later
Description
The ScoreboardPath directive sets the directory where proftpd run-time scoreboard
files (proftpd-*) are kept. These file(s) are necessary for MaxClients
to work properly, as well as other utilities (such as ftpwho and ftpcount).See alsoExamples
mod_core
ServerAdmin
ServerAdmin
ServerAdminSet the address for the server adminServerAdminDefault
ServerAdmin root@[ServerName]
Context
server config, <VirtualHost>
Module
mod_core
Compatibility
0.99.0pl10 and later
Description
The ServerAdmin directive sets the email address of the administrator for
the server or virtualhost. This address is displayed in magic cookie replacements
(see DisplayLogin and DisplayFirstChdir).See alsoExamples
mod_core
ServerIdent
ServerIdent
ServerIdentSet the message displayed on connectServerIdentDefault
ServerIdent ProFTPD [version] Server (server name) [hostname]
Context
server config, <VirtualHost>, <Global>
Module
mod_core
Compatibility
1.2.0pre2 and later
Description
The ServerIdent directive sets the default message displayed when a new client
connects. Setting this to off displays "[hostname]
FTP server ready." If set to on, the directive
can take an optional string argument, which will be displayed instead of the
default text. Sites desiring to give out minimal information will probably
want a setting like ServerIdent on "FTP Server ready.", which won't
even reveal the hostname. See alsoExamples
ServerIdent on "Welcome to ftp.linux.co.uk"
mod_core
ServerName
ServerName
ServerNameConfigure the name displayed to connecting usersServerNameDefault
ServerName "ProFTPD Server [version]"
Context
server config, <VirtualHost>
Module
mod_core
Compatibility
0.99.0 and later
Description
The ServerName directive configures the string that will be displayed to
a user connecting to the server (or virtual server if the directive is located
in a <VirtualHost> block).
See Also: <VirtualHost>See alsoExamples
mod_core
ServerType
ServerType
ServerTypeSet the mode proftpd runs inServerTypeDefault
ServerType standalone
Context
server config
Module
mod_core
Compatibility
0.99.0 and later
Description
The ServerType directive configures the server daemon's operating mode. The
type-identifier can be one of two values:
inetd
The daemon will expect to be run from the inetd "super server."
New connections are passed from inetd to proftpd and serviced immediately.
standalone
The daemon starts and begins listening to the configured port for incoming connections. New connections
result in spawned child processes dedicated to servicing all requests from
the newly connected client.See alsoExamples
mod_ls
ShowDotFiles
ShowDotFiles
ShowDotFilesToggle display of 'dotfiles'ShowDotFilesDefault
ShowDotFiles Off
Context
server config, <VirtualHost>, <Anonymous>, <Global>
Module
mod_ls
Compatibility
0.99.0pl6 and later -- Deprecated
Description
If set to on, files starting with a '.', except for the
directories '.' and '..', will be displayed in
directory listings. This directive has been deprecated in favor of
LsDefaultOptions -- e.g., LsDefaultOptions
"-A" -- and may be removed in future versions.
See Also: LsDefaultOptionsSee alsoExamples
mod_core
ShowSymlinks
ShowSymlinks
ShowSymlinksToggle the display of symlinksShowSymlinksDefault
(versions 1.1.5 and beyond) ShowSymlinks On
Context
server config, <VirtualHost>, <Anonymous>, <Global>
Module
mod_core
CompatibilityDescription
Compatibility: 0.99.0pl6 and later
Symbolic links (if supported on the host OS and filesystem) can be either
shown in directory listings (including the target of the link) or can be "hidden"
(proftpd dereferences symlinks and reports the target's permissions and ownership).
The default behavior is to show all symbolic links when normal users are logged
in, and hide them for anonymous sessions. If a symbolic link cannot be dereferenced
for any reason (permissions, target does not exist, etc) and ShowSymlinks
is off, proftpd displays the link as a directory entry of type 'l' (link)
with the ownership and permissions of the actual link.
Under ProFTPD versions 1.1.5 and higher, the default behavior in regard to
ShowSymlinks has been changed so that symbolic links are always displayed
as such (in all cases), unless ShowSymlinks off is explicitly set.See alsoExamples
mod_core
SocketBindTight
SocketBindTight
SocketBindTightControls how TCP/IP sockets are createdSocketBindTightDefault
SocketBindTight off
Context
server config
Module
mod_core
Compatibility
0.99.0pl6 and later
Description
The SocketBindTight directive controls how proftpd creates and binds its
initial tcp listen sockets in standalone mode (see
ServerType). The directive has no effect upon servers
running in inetd mode, because listen sockets are
not needed or created. When SocketBindTight is set to off
(the default), a single listening socket is created for each port that the
server must listen on, regardless of the number of IP addresses being used
by <VirtualHost> configurations. This has
the benefit of typically requiring a relatively small number of file descriptors
for the master daemon process, even if a large number of virtual servers are
configured. If SocketBindTight is set to on, a listen
socket is created and bound to a specific IP address for the master server
and all configured virtual servers. This allows for situations where an administrator
may wish to have a particular port be used by both proftpd (on one IP address)
and another daemon (on a different IP address). The drawback is that considerably
more file descriptors will be required if a large number of virtual servers
must be supported.
Example: Two servers have been configured (one master and one virtual), with
the IP addresses 10.0.0.1 and 10.0.0.2, respectively. The 10.0.0.1 server
runs on port 21, while 10.0.0.2 runs on port 2001.
SocketBindTight off #default
# proftpd creates two sockets, both bound to ALL available addresses.
# one socket listens on port 21, the other on 2001. Because each socket is
# bound to all available addresses, no other daemon or user process will be
# allowed to bind to ports 21 or 2001.
...
SocketBindTight on
# proftpd creates two sockets again, however one is bound to 10.0.0.1, port
21
# and the other to 10.0.0.2, port 2001. Because these sockets are "tightly"
# bound to IP addresses, port 21 can be reused on any address OTHER than
# 10.0.0.1, and visa-versa with 10.0.0.2, port 2001.
One side-effect of setting SocketBindTight to on
is that connections to non-bound addresses will result in a "connection
refused" message rather than the typical "500 Sorry, no server available
to handle request on xxx.xxx.xxx.xxx.", due to the fact that no listen
socket has been bound to the particular address/port pair. This may or may
not be aesthetically desirable, depending on your circumstances.See alsoExamples
mod_sql
SQLAuthenticate
SQLAuthenticate
SQLAuthenticateFIXFIXFIXSQLAuthenticateDefault
FIXFIXFIX
Context
server config, <Global>, <VirtualHost>, <Anonymous>, <Limit>, .ftpaccess
Module
mod_sql
Compatibility
1.2.5rc1 and later
Description
FIX FIX FIX
See alsoExamples
FIXFIXFIX
FIXFIX
mod_sql
SQLAuthoritative
SQLAuthoritative
SQLAuthoritativeFIXFIXFIXSQLAuthoritativeDefault
FIXFIXFIX
Context
server config, <Global>, <VirtualHost>, <Anonymous>, <Limit>, .ftpaccess
Module
mod_sql
Compatibility
1.2.5rc1 and later
Description
FIX FIX FIX
See alsoExamples
FIXFIXFIX
FIXFIX
mod_sql
SQLAuthTypes
SQLAuthTypes
SQLAuthTypesFIXME FIXMESQLAuthTypesDefault
none
Context
server config, <Global>, <VirtualHost>
Module
mod_sql
Compatibility
1.2.0 and later
Description
This directive deprecates 'SQLEmptyPasswords',
'SQLScrambledPasswords', 'SQLSSLHashedPasswords',
'SQLPlaintextPasswords', and 'SQLEncryptedPasswords'.
Specifies the allowed authentication types and their check order. YOU
MUST SPECIFY AT LEAST ONE AUTHENTICATION METHOD.
For example:
SQLAuthTypes Crypt Empty
means check whether the password in the database matches in UNIX
crypt() format; if that fails, check to see if the password in the
database is empty (matching ANY given password); if that fails,
mod_sql refuses to authenticate the user.
Current Types
Plaintext: allows passwords in the database to be in plaintext
OpenSSL: allows passwords in the database to be of the form
'{digestname}hashedvalue'. This check is only available if
you define 'HAVE_OPENSSL' when you compile proftd and you
link with the OpenSSL 'crypto' library.
Crypt: allows passwords in the database to be in UNIX crypt() form
Backend: a database-specific backend check function. Not all
backends support this. Specifically, the MySQL backend
uses this type to authenticate MySQL 'PASSWORD()' encrypted
passwords. The Postgres backend does nothing.
Empty: allows empty passwords in the database, which match against
ANYTHING the user types in. The database field must be a
truly empty string -- that is, NULL values are never
accepted. BE VERY CAREFUL WITH THIS AUTHTYPE.
mod_sql
SQLConnectInfo
SQLConnectInfo
SQLConnectInfoFIXME FIXMESQLConnectInfoDefault
none
Context
server config, <Global>, <VirtualHost>
Module
mod_sql
Compatibility
1.2.0 and later
Description
This directive deprecates 'MySQLInfo', 'PostgresInfo', and
'PostgresPort'.
Specifies connection information. Connection-info specifies the
database, host, port, and other backend-specific information.
username and password specify the username and password to connect as,
respectively. Both default to NULL, which the backend will treat in
some backend-specific manner. If you specify a password, you MUST
specify a username.
Any given backend has the opportunity (but not the responsibility) to
check for syntax errors in the connection-info field at proftpd
startup, but you shouldn't expect semantic errors (i.e., can't connect
to the database) to be caught until mod_sql attempts to connect for a
given host.
The MySQL and Postgres backends connection-info is expected to be of
the form:
database[@hostname][:port]
hostname will default to a backend-specific hostname (which happens to
be 'localhost' for both the MySQL and Postgres backends), and port
will default to a backend-specific default port (3306 for the MySQL
backend, 5432 for the Postgres backend).
Examples:
SQLConnectInfo ftpusers@foo.com
means "Try connecting to the database 'ftpuser' via the default port
at 'foo.com'. Use a NULL username and a NULL password."
SQLConnectInfo ftpusers:3000 admin
means "Try connecting to the database 'ftpuser' via port 3000 at
'localhost'. Use the username 'admin' and a NULL password."
SQLConnectInfo ftpusers@foo.com:3000 admin mypassword
means "Try connecting to the database 'ftpuser' via port 3000 at
'foo.com'. Use the username 'admin' and the password 'mypassword'"
Backends may require different information in the connection-info
field; check your backend module for specifics.
mod_sql
SQLDefaultGID
SQLDefaultGID
SQLDefaultGIDFIXME FIXMESQLDefaultGIDDefault
65533
Context
server config, <Global>, <VirtualHost>
Module
mod_sql
Compatibility
1.2.0 and later
Description
Sets the default GID for users. Must be greater than SQLMinID.
mod_sql
SQLDefaultHomedir
SQLDefaultHomedir
SQLDefaultHomedirFIXFIXFIXSQLDefaultHomedirDefault
FIXFIXFIX
Context
server config, <Global>, <VirtualHost>, <Anonymous>, <Limit>, .ftpaccess
Module
mod_sql
Compatibility
1.2.5rc1 and later
Description
FIX FIX FIX
See alsoExamples
FIXFIXFIX
FIXFIX
mod_sql
SQLDefaultUID
SQLDefaultUID
SQLDefaultUIDFIXME FIXMESQLDefaultUIDDefault
65533
Context
server config, <Global>, <VirtualHost>
Module
mod_sql
Compatibility
1.2.0 and later
Description
Sets the default UID for users. Must be greater than SQLMinID.
mod_sql
SQLDoAuth
SQLDoAuth
SQLDoAuthFIXME FIXMESQLDoAuthDefault
on
Context
server config, <Global>, <VirtualHost>
Module
mod_sql
Compatibility
1.2.0 and later
Description
Activates SQL authentication. This overrides all other directives --
SQLDoGroupAuth and SQLAuthoritative are ineffectual if SQLDoAuth is off.
mod_sql
SQLDoGroupAuth
SQLDoGroupAuth
SQLDoGroupAuthFIXME FIXMESQLDoGroupAuthDefault
on
Context
server config, <Global>, <VirtualHost>
Module
mod_sql
Compatibility
1.2.0 and later
Description
This directive causes mod_sql to pretend it has no group information.
It necessarily breaks ALL CONFIG FILES up to 1.2.0rc2, since mod_sql
now assumes that group information is available UNLESS this directive
is set to OFF.
This DOESN'T override SQLAuthoritative -- if SQLAuthoritative is set
to 'On' but SQLDoGroupAuth is set to 'Off', all group-related queries
will fail without giving other modules the opportunity to handle them.
Prior to 1.2.0, there was no way to provide group information from the
database. This caused a few bugs, and reduced the functionality of
this module.
mod_sql
SQLEmptyPasswords
SQLEmptyPasswords
SQLEmptyPasswordsAllow zero length passwords (DEPRECATED)SQLEmptyPasswordsDefault
off
Context
server config, <Global>, <VirtualHost>
Module
mod_sql
Compatibility
1.2.0rc2 and later
DescriptionThis directive is deprecated, please use SQLAuthTypes instead
Specifies whether an empty (non-NULL but zero-length) password is
acceped from the database. Default is no, and truly NULL passwords
are never accepted. If the retrieved password is empty then whatever
password the user typed is accepted as valid, but the module logs a
warning at debug level 4.See alsoExamples
SQLEmptyPasswords on
mod_sql
SQLEncryptedPasswords
SQLEncryptedPasswords
SQLEncryptedPasswordsAssume SQL passwords are encrypted (DEPRECATED)SQLEncryptedPasswordsDefault
on
Context
server config
Module
mod_sql
Compatibility
1.2.0rc2 and later
DescriptionThis directive is deprecated, please SQLAuthTypes instead
Specifies whether the password in the database may be in UNIX crypt()
format. Default is true, with this being the only check done. A tool
for generating crypted password text may be found at
ftp://ftp.linpeople.org/pub/People/lilo/source/makepasswd-1.07.tar.gzSee alsoExamples
SQLEncryptedPasswords on
mod_sql
SQLGidField
SQLGidField
SQLGidFieldFIXFIXFIXSQLGidFieldDefault
FIXFIXFIX
Context
server config, <Global>, <VirtualHost>, <Anonymous>, <Limit>, .ftpaccess
Module
mod_sql
Compatibility
1.2.5rc1 and later
Description
FIX FIX FIX
See alsoExamples
FIXFIXFIX
FIXFIX
mod_sql
SQLGroupGIDField
SQLGroupGIDField
SQLGroupGIDFieldFIXFIXFIXSQLGroupGIDFieldDefault
FIXFIXFIX
Context
server config, <Global>, <VirtualHost>, <Anonymous>, <Limit>, .ftpaccess
Module
mod_sql
Compatibility
1.2.5rc1 and later
Description
FIX FIX FIX
See alsoExamples
FIXFIXFIX
FIXFIX
mod_sql
SQLGroupInfo
SQLGroupInfo
SQLGroupInfoFIXFIXFIXSQLGroupInfoDefault
FIXFIXFIX
Context
server config, <Global>, <VirtualHost>, <Anonymous>, <Limit>, .ftpaccess
Module
mod_sql
Compatibility
1.2.5rc1 and later
Description
FIX FIX FIX
See alsoExamples
FIXFIXFIX
FIXFIX
mod_sql
SQLGroupMembersField
SQLGroupMembersField
SQLGroupMembersFieldFIXME FIXMESQLGroupMembersFieldDefault
members
Context
server config, <Global>, <VirtualHost>
Module
mod_sql
Compatibility
1.2.0 and later
Description
Specifies the field in the group table that holds the group's member
list.
mod_sql
SQLGroupnameField
SQLGroupnameField
SQLGroupnameFieldFIXME FIXMESQLGroupnameFieldDefault
groupname
Context
server config, <Global>, <VirtualHost>
Module
mod_sql
Compatibility
1.2.0 and later
Description
Specifies the field in the group table that holds the group name.
mod_sql
SQLGroupTable
SQLGroupTable
SQLGroupTableFIXME FIXMESQLGroupTableDefault
groups
Context
server config, <Global>, <VirtualHost>
Module
mod_sql
Compatibility
1.2.0 and later
Description
Specifies the name of the table that holds group information.
mod_sql
SQLGroupWhereClause
SQLGroupWhereClause
SQLGroupWhereClauseFIXFIXFIXSQLGroupWhereClauseDefault
FIXFIXFIX
Context
server config, <Global>, <VirtualHost>, <Anonymous>, <Limit>, .ftpaccess
Module
mod_sql
Compatibility
1.2.5rc1 and later
Description
FIX FIX FIX
See alsoExamples
FIXFIXFIX
FIXFIX
mod_sql
SQLHomedir
SQLHomedir
SQLHomedirFIXFIXFIXSQLHomedirDefault
FIXFIXFIX
Context
server config, <Global>, <VirtualHost>, <Anonymous>, <Limit>, .ftpaccess
Module
mod_sql
Compatibility
1.2.5rc1 and later
Description
FIX FIX FIX
See alsoExamples
FIXFIXFIX
FIXFIX
mod_sql
SQLHomedirField
SQLHomedirField
SQLHomedirFieldFIXFIXFIXSQLHomedirFieldDefault
FIXFIXFIX
Context
server config, <Global>, <VirtualHost>, <Anonymous>, <Limit>, .ftpaccess
Module
mod_sql
Compatibility
1.2.5rc1 and later
Description
FIX FIX FIX
See alsoExamples
FIXFIXFIX
FIXFIX
mod_sql
SQLHomedirOnDemand
SQLHomedirOnDemand
SQLHomedirOnDemandFIXME FIXMESQLHomedirOnDemandDefault
off
Context
server config, <Global>, <VirtualHost>
Module
mod_sql
Compatibility
1.2.0 and later
Description
Specifies whether to automatically create a user's home directory if
it doesn't exist at login.
mod_sql
SQLLog
SQLLog
SQLLogFIXFIXFIXSQLLogDefault
FIXFIXFIX
Context
server config, <Global>, <VirtualHost>, <Anonymous>, <Limit>, .ftpaccess
Module
mod_sql
Compatibility
1.2.5rc1 and later
Description
FIX FIX FIX
See alsoExamples
FIXFIXFIX
FIXFIX
mod_sql
SQLLogDirs
SQLLogDirs
SQLLogDirsFIXFIXFIXSQLLogDirsDefault
FIXFIXFIX
Context
server config, <Global>, <VirtualHost>, <Anonymous>, <Limit>, .ftpaccess
Module
mod_sql
Compatibility
1.2.5rc1 and later
Description
FIX FIX FIX
See alsoExamples
FIXFIXFIX
FIXFIX
mod_sql
SQLLogHits
SQLLogHits
SQLLogHitsFIXFIXFIXSQLLogHitsDefault
FIXFIXFIX
Context
server config, <Global>, <VirtualHost>, <Anonymous>, <Limit>, .ftpaccess
Module
mod_sql
Compatibility
1.2.5rc1 and later
Description
FIX FIX FIX
See alsoExamples
FIXFIXFIX
FIXFIX
mod_sql
SQLLogHosts
SQLLogHosts
SQLLogHostsFIXFIXFIXSQLLogHostsDefault
FIXFIXFIX
Context
server config, <Global>, <VirtualHost>, <Anonymous>, <Limit>, .ftpaccess
Module
mod_sql
Compatibility
1.2.5rc1 and later
Description
FIX FIX FIX
See alsoExamples
FIXFIXFIX
FIXFIX
mod_sql
SQLLoginCountField
SQLLoginCountField
SQLLoginCountFieldFIXFIXFIXSQLLoginCountFieldDefault
FIXFIXFIX
Context
server config, <Global>, <VirtualHost>, <Anonymous>, <Limit>, .ftpaccess
Module
mod_sql
Compatibility
1.2.5rc1 and later
Description
FIX FIX FIX
See alsoExamples
FIXFIXFIX
FIXFIX
mod_sql
SQLLogStats
SQLLogStats
SQLLogStatsFIXFIXFIXSQLLogStatsDefault
FIXFIXFIX
Context
server config, <Global>, <VirtualHost>, <Anonymous>, <Limit>, .ftpaccess
Module
mod_sql
Compatibility
1.2.5rc1 and later
Description
FIX FIX FIX
See alsoExamples
FIXFIXFIX
FIXFIX
mod_sql
SQLMinID
SQLMinID
SQLMinIDFIXME FIXMESQLMinIDDefault
999
Context
server config, <Global>, <VirtualHost>
Module
mod_sql
Compatibility
1.2.0 and later
Description
SQLMinID is checked whenever retrieving a user's GID or UID. If the
retrieved values for GID or UID are less than the value of SQLMinID,
they are reported as the values of, respectively, 'SQLDefaultGID' and
'SQLDefaultUID'.
mod_sql
SQLMinUserGID
SQLMinUserGID
SQLMinUserGIDFIXFIXFIXSQLMinUserGIDDefault
FIXFIXFIX
Context
server config, <Global>, <VirtualHost>, <Anonymous>, <Limit>, .ftpaccess
Module
mod_sql
Compatibility
1.2.5rc1 and later
Description
FIX FIX FIX
See alsoExamples
FIXFIXFIX
FIXFIX
mod_sql
SQLMinUserUID
SQLMinUserUID
SQLMinUserUIDFIXFIXFIXSQLMinUserUIDDefault
FIXFIXFIX
Context
server config, <Global>, <VirtualHost>, <Anonymous>, <Limit>, .ftpaccess
Module
mod_sql
Compatibility
1.2.5rc1 and later
Description
FIX FIX FIX
See alsoExamples
FIXFIXFIX
FIXFIX
mod_sql
SQLNamedQuery
SQLNamedQuery
SQLNamedQueryFIXFIXFIXSQLNamedQueryDefault
FIXFIXFIX
Context
server config, <Global>, <VirtualHost>, <Anonymous>, <Limit>, .ftpaccess
Module
mod_sql
Compatibility
1.2.5rc1 and later
Description
FIX FIX FIX
See alsoExamples
FIXFIXFIX
FIXFIX
mod_sql
SQLPasswordField
SQLPasswordField
SQLPasswordFieldFIXFIXFIXSQLPasswordFieldDefault
FIXFIXFIX
Context
server config, <Global>, <VirtualHost>, <Anonymous>, <Limit>, .ftpaccess
Module
mod_sql
Compatibility
1.2.5rc1 and later
Description
FIX FIX FIX
See alsoExamples
FIXFIXFIX
FIXFIX
mod_sql
SQLProcessGrEnt
SQLProcessGrEnt
SQLProcessGrEntFIXFIXFIXSQLProcessGrEntDefault
FIXFIXFIX
Context
server config, <Global>, <VirtualHost>, <Anonymous>, <Limit>, .ftpaccess
Module
mod_sql
Compatibility
1.2.5rc1 and later
Description
FIX FIX FIX
See alsoExamples
FIXFIXFIX
FIXFIX
mod_sql
SQLProcessPwEnt
SQLProcessPwEnt
SQLProcessPwEntFIXFIXFIXSQLProcessPwEntDefault
FIXFIXFIX
Context
server config, <Global>, <VirtualHost>, <Anonymous>, <Limit>, .ftpaccess
Module
mod_sql
Compatibility
1.2.5rc1 and later
Description
FIX FIX FIX
See alsoExamples
FIXFIXFIX
FIXFIX
mod_sql
SQLRatios
SQLRatios
SQLRatiosFIXFIXFIXSQLRatiosDefault
FIXFIXFIX
Context
server config, <Global>
Module
mod_sql
Compatibility
1.2.5rc1 and later
Description
FIX FIX FIX
See alsoExamples
FIXFIXFIX
FIXFIX
mod_sql
SQLRatioStats
SQLRatioStats
SQLRatioStatsFIXFIXFIXSQLRatioStatsDefault
FIXFIXFIX
Context
server config, <Global>
Module
mod_sql
Compatibility
1.2.5rc1 and later
Description
FIX FIX FIX
See alsoExamples
FIXFIXFIX
FIXFIX
mod_sql
SQLScrambledPasswords
SQLScrambledPasswords
SQLScrambledPasswordsFIXME FIXMESQLScrambledPasswordsDefault
off
Context
server config, <Global>, <VirtualHost>
Module
mod_sql
Compatibility
1.2.0 and later
Description
This directive is DEPRECATED. Please use SQLAuthTypes instead.
Specifies whether to accept passwords in a backend specific format.
For the MySQL backend, this means 'PASSWORD()' scrambled passwords.
For the Postgres backend, this check does nothing.
mod_sql
SQLShellField
SQLShellField
SQLShellFieldFIXME FIXMESQLShellFieldDefault
shell
Context
server config, <Global>, <VirtualHost>
Module
mod_sql
Compatibility
1.2.0 and later
Description
Specifies the field in the user table that holds the user's shell. If
this field doesn't exist or the result of the query is NULL, the shell
is reported as "".
mod_sql
SQLShowInfo
SQLShowInfo
SQLShowInfoFIXFIXFIXSQLShowInfoDefault
FIXFIXFIX
Context
server config, <Global>, <VirtualHost>, <Anonymous>, <Limit>, .ftpaccess
Module
mod_sql
Compatibility
1.2.5rc1 and later
Description
FIX FIX FIX
See alsoExamples
FIXFIXFIX
FIXFIX
mod_sql
SQLSSLHashedPasswords
SQLSSLHashedPasswords
SQLSSLHashedPasswordsFIXME FIXMESQLSSLHashedPasswordsDefault
off
Context
server config, <Global>, <VirtualHost>
Module
mod_sql
Compatibility
1.2.0 and later
Description
This directive is DEPRECATED. Please use SQLAuthTypes instead.
Specifies whether to accept passwords of the form
{digestname}hashedpassword from the database. This directive is only
available if you define 'HAVE_OPENSSL' when you compile proftd and you
link with the OpenSSL 'crypto' library. As an example, any of the
following password entries in the database would match if the user
typed the password 'testpassword':
{SHA}IoFZRnP0iujh/70lps6DjKPgwkk=
{SHA1}i7YRj4/Wk1rQh2o740pxfTJwj/0=
{MD2}nS6iguewvAdrCnOMyQjB1w==
{MD4}5wsGtJCkyXBzDJoVsQKjSg==
{MD5}4WsquNEjFL9O+9YgOQbqbA==
mod_sql
SQLUidField
SQLUidField
SQLUidFieldFIXFIXFIXSQLUidFieldDefault
FIXFIXFIX
Context
server config, <Global>, <VirtualHost>, <Anonymous>, <Limit>, .ftpaccess
Module
mod_sql
Compatibility
1.2.5rc1 and later
Description
FIX FIX FIX
See alsoExamples
FIXFIXFIX
FIXFIX
mod_sql
SQLUserInfo
SQLUserInfo
SQLUserInfoFIXFIXFIXSQLUserInfoDefault
FIXFIXFIX
Context
server config, <Global>, <VirtualHost>, <Anonymous>, <Limit>, .ftpaccess
Module
mod_sql
Compatibility
1.2.5rc1 and later
Description
FIX FIX FIX
See alsoExamples
FIXFIXFIX
FIXFIX
mod_sql
SQLUsernameField
SQLUsernameField
SQLUsernameFieldFIXFIXFIXSQLUsernameFieldDefault
FIXFIXFIX
Context
server config, <Global>, <VirtualHost>, <Anonymous>, <Limit>, .ftpaccess
Module
mod_sql
Compatibility
1.2.5rc1 and later
Description
FIX FIX FIX
See alsoExamples
FIXFIXFIX
FIXFIX
mod_sql
SQLUserTable
SQLUserTable
SQLUserTableFIXFIXFIXSQLUserTableDefault
FIXFIXFIX
Context
server config, <Global>, <VirtualHost>, <Anonymous>, <Limit>, .ftpaccess
Module
mod_sql
Compatibility
1.2.5rc1 and later
Description
FIX FIX FIX
See alsoExamples
FIXFIXFIX
FIXFIX
mod_sql
SQLUserWhereClause
SQLUserWhereClause
SQLUserWhereClauseFIXFIXFIXSQLUserWhereClauseDefault
FIXFIXFIX
Context
server config, <Global>, <VirtualHost>, <Anonymous>, <Limit>, .ftpaccess
Module
mod_sql
Compatibility
1.2.5rc1 and later
Description
FIX FIX FIX
See alsoExamples
FIXFIXFIX
FIXFIX
mod_sql
SQLWhereClause
SQLWhereClause
SQLWhereClauseFIXME FIXMESQLWhereClauseDefault
none
Context
server config, <Global>, <VirtualHost>
Module
mod_sql
Compatibility
1.2.0 and later
Description
This directive deprecates 'SQLKey' and 'SQLKeyField'.
Specifies a where clause that is added to every user query (this has
no effect on group queries). The where clause *must* contain all
relevant punctuation, and *must not* contain a leading 'and'.
As an example of switching from the old-style 'SQLKey' and
'SQLKeyField' directives, if you had:
SQLKey true
SQLKeyfield LoginAllowed
You would now use:
SQLWhereClause "LoginAllowed = 'true'"
This would be appended to every user-related query as the string
" and (LoginAllowed = 'true')"
mod_core
SyslogFacility
SyslogFacility
SyslogFacilitySet the facility level used for loggingSyslogFacilityDefault
None
Context
server config
Module
mod_core
Compatibility
1.1.6 and later
Description
Proftpd logs its activity via the Unix syslog mechanism, which allows for
several different general classifications of logging messages, known as "facilities."
Normally, all authentication related messages are logged with the AUTHPRIV
(or AUTH) facility [intended to be secure, and never seen by unwanted eyes],
while normal operational messages are logged with the DAEMON facility. The
SyslogFacility directive allows ALL logging messages to be directed to a different
facility than the default. When this directive is used, ALL logging is done
with the specified facility, both authentication (secure) and otherwise.
The facility-level argument must be one of the
following: AUTH (or AUTHPRIV), CRON,
DAEMON, KERN, LPR, MAIL, NEWS, USER, UUCP, LOCAL0, LOCAL1, LOCAL2, LOCAL3,
LOCAL4, LOCAL5, LOCAL6 or LOCAL7.
See Also: SystemLogSee alsoExamples
mod_core
SyslogLevel
SyslogLevel
SyslogLevelSet the verbosity level of system loggingSyslogLevelDefault
None
Context
server config, <VirtualHost>, <Anonymous>, <Global>
Module
mod_core
Compatibility
1.2.0rc2+cvs and later
Description
SyslogLevel adjusts the verbosity of the messages recorded in the
error logs. The following levels are available, in order
of decreasing significance:
Level
Description
emerg
Emergencies - system is unusable.
alert
Action must be taken immediately.
crit
Critical Conditions.
error
Error conditions.
warn
Warning conditions.
notice
Normal but significant condition.
info
Informational.
debug
Debug-level messages
When a particular level is specified, messages from all other
levels of higher significance will be reported as well.
E.g., when SyslogLevel info is specified, then
messages with log levels of notice and
warn will also be posted.
Using a level of at least crit is recommended.See alsoExamples
mod_log
SystemLog
SystemLog
SystemLogRedirect syslogging to a fileSystemLogDefault
None
Context
server config
Module
mod_log
Compatibility
1.1.6pl1 and later
Description
The SystemLog directive disables proftpd's use of the syslog mechanism and
instead redirects all logging output to the specified filename.
The filename argument should contain an absolute
path, and should not be to a file in a nonexistent directory, in a
world-writeable directory, or be a symbolic link (unless AllowLogSymlinks
is set to on). Use of this directive overrides any facility set by the
SyslogFacility directive. Additionally, the special keyword NONE can be used
which disables all syslog style logging for the entire configuration.See also
AllowLogSymlinks
Examples
mod_wrap
TCPAccessFiles
TCPAccessFiles
TCPAccessFilesSets the access files to useTCPAccessFilesDefault
none
Context
server config, <VirtualHost>, <Global>, <Anonymous>
Module
mod_wrap
Compatibility
1.2.1 and later
Description
TCPAccessFiles specifies two files, an allow and a deny file, each
of which contain the IP addresses, networks or name-based masks to be
allowed or denied connections to the server. The files have the same
format as the standard tcpwrappers hosts.allow/deny files.
Both file names are required. Also, the paths to both files must
be the full path, with two exceptions: if the path starts with ~/, the
check of that path will be delayed until a user requests a connection,
at which time the path will be resolved to that user's home directory;
or if the path starts with ~user/, where user is some system user. In
this latter case, mod_wrap will attempt to resolve and verify the given
user's home directory on start-up.
The service name for which mod_wrap will look in the indicated
access files is proftpd by default; this can be configured via the
TCPServiceName directive. There is a built-in precedence to the
TCPAccessFiles, TCPGroupAccessFiles, and TCPUserAccessFiles directives,
if all are used. mod_wrap will look for applicable TCPUserAccessFiles
for the connecting user first. If no applicable TCPUserAccessFiles is
found, mod_wrap will search for TCPGroupAccessFiles which pertain to
the connecting user. If not found, mod_wrap will then look for the
server-wide TCPAccessFiles directive. This allows for access control to
be set on a per-server basis, and allow for per-user or per-group access
control to be handled without interfering with the server access rules.
See also
TCPGroupAccessFiles,
TCPServiceName,
TCPUserAccessFiles
Examples
# server-wide access files
TCPAccessFiles /etc/ftpd.allow /etc/ftpd.deny
# per-user access files, which are to be found in the user's home directory
TCPAccessFiles ~/my.allow ~/my.deny
mod_wrap
TCPAccessSyslogLevels
TCPAccessSyslogLevels
TCPAccessSyslogLevelsSets the logging levels for mod_wrapTCPAccessSyslogLevelsDefault
TCPAccessSyslogLevels info warn
Context
server config, <VirtualHost>, <Global>, <Anonymous>
Module
mod_wrap
Compatibility
1.2.1 and later
Description
ProFTPD can log when a connection is allowed, or denied, as the result
of rules in the files specified in TCPAccessFiles, to the Unix syslog
mechanism. A discussion on the syslog levels which can be used is given
in the SyslogLevel directive.
The allow-level parameter sets the syslog level at which allowed connections
are logged; the deny-level parameter sets the syslog level for denied
connections.
See also
SyslogLevel
Examples
TCPAccessSyslogLevels debug warn
mod_core
tcpBackLog
tcpBackLog
tcpBackLogControl the tcp backlog in standalone modetcpBackLogDefault
tcpBackLog 5
Context
server config
Module
mod_core
Compatibility
0.99.0 and later
Description
The tcpBackLog directive controls the tcp "backlog queue" when
listening for connections in standalone mode (see
ServerType). It has no affect upon
servers in inetd mode. When a tcp connection is
established by the tcp/ip stack inside the kernel, there is a short period
of time between the actual establishment of the connection and the acceptance
of the connection by a user-space program. The duration of this latency period
is widely variable, and can depend upon several factors (hardware, system
load, etc). During this period tcp connections cannot be accepted, as the
port that was previously "listening" has become filled with the
new connection. Under heavy connection load this can result in occasional
(or even frequent!) "connection refused" messages returned to the
incoming client, even when there is a service available to handle requests.
To eliminate this problem, most modern tcp/ip stacks implement a "backlog
queue" which is simply a pre-allocation of resources necessary to handle
backlog-size connections during the latency period.
The larger the backlog queue, the more connections can be established in a
very short time period. The trade-off, of course, is kernel memory and/or
other kernel resources.
Generally it is not necessary to use a tcpBackLog directive, unless you intend
to service a large number of virtual hosts (see <VirtualHost>),
or have a consistently heavy system load. If you begin to notice or hear of
"connection refused" messages from remote clients, try setting a
slightly higher value to this directive.See alsoExamples
mod_wrap
TCPGroupAccessFiles
TCPGroupAccessFiles
TCPGroupAccessFilesSets the access files to useTCPGroupAccessFilesDefault
none
Context
server config, <VirtualHost>, <Global>
Module
mod_wrap
Compatibility
1.2.1 and later
Description
TCPGroupAccessFiles allows for access control files, the same types of
files required by TCPAccessFiles, to be applied to select groups. The
given group-expression is a logical AND expression, which means that
the connecting user must be a member of all the groups listed for this
directive to apply. Group names may be negated with a ! prefix.
The rules for the filename paths are the same as for TCPAccessFiles settings.
See also
TCPAccessFiles,
TCPUserAccessFiles
Examples
# every member of group wheel must connect from restricted locations
TCPGroupAccessFiles wheel /etc/ftpd-strict.allow /etc/ftpd-strict.deny
# everyone else gets the standard access rules
TCPGroupAccessFiles !wheel /etc/hosts.allow /etc/hosts.deny
mod_core
tcpNoDelay
tcpNoDelay
tcpNoDelayControl the use of TCP_NODELAYtcpNoDelayDefault
tcpNoDelay on
Context
server config, <VirtualHost>, <Global>
Module
mod_core
Compatibility
1.2.0pre3a and later
Description
The tcpNoDelay directive controls the use of the TCP_NODELAY socket option
(which disables the Nagle algorithm). ProFTPd uses TCP_NODELAY by default,
which usually is a benefit but this can occasionally lead to problems with
some clients, so tcpNoDelay is provided as a way to disable this option. You
will not normally need to use this directive but if you have clients reporting
unusually slow connections, try setting this to off. See alsoExamples
mod_core
tcpReceiveWindow
tcpReceiveWindow
tcpReceiveWindowSet the size of the tcp receive windowtcpReceiveWindowDefault
tcpReceiveWindow 8192
Context
server config, <VirtualHost>
Module
mod_core
Compatibility
0.99.0 and later
Description
The tcpReceiveWindow directive configures the size (in octets) of all data
connections' tcp receive windows. It is only used when receiving a file from
a client over the data connection. Typically, a given tcp/ip implementation
will use a relatively small receive window size (the number of octets that
can be received at the tcp layer before a "turnaround" acknowledgement
is required). When transferring a large amount of data over fast digital transmission
lines which have a relatively high latency, a small receive window can dramatically
affect perceived throughput because of the necessity to completely stop the
transfer occasionally in order to wait for the remote endpoint to receive
the acknowledgement and continue transmission. For example, on a T1 line (assuming
full 1.544Mbps endpoint-to-endpoint throughput) with 100 ms latency, a 4k
receive buffer will very dramatically reduce the perceived throughput. The
default value of 8192 octets (8k) should be reasonable in common network configurations.
Additionally, proftpd allocates its internal buffers to match the receive/send
window sizes; in order to maximize the reception/transmission performance
(reducing the number of times data must be transfered from proftpd to the
kernel tcp/ip stack). The tradeoff, of course, is memory; both kernel- and
user-space. If running proftpd on a memory tight host (and on a low-bandwidth
connection), it might be advisable to decrease both the tcpReceiveWindow and
tcpSendWindow sizes.See alsoExamples
mod_core
tcpSendWindow
tcpSendWindow
tcpSendWindowSet the size of the tcp send windowtcpSendWindowDefault
tcpSendWindow 8192
Context
server config, <VirtualHost>
Module
mod_core
Compatibility
0.99.0 and later
Description
The tcpSendWindow directive configures the size (in octets) of all data connections'
tcp send windows. It is only used when sending a file from the server to a
client on the data connection. For a detailed description of receive/send
window sizes see tcpReceiveWindow.See alsoExamples
mod_wrap
TCPServiceName
TCPServiceName
TCPServiceNameConfigures the name proftpd will use with mod_wrapTCPServiceNameDefault
TCPServiceName proftpd
Context
server config, <VirtualHost>, <Global>
Module
mod_wrap
Compatibility
1.2.1 and later
Description
TCPServiceName is used to configure the name of the service under which mod_wrap will check the allow/deny files. By default, this is the name of the program started, i.e. "proftpd". However, some administrators may want to use a different, more generic service name, such as "ftpd"; use this directive for such needs.
See also
mod_wrap
TCPUserAccessFiles
TCPUserAccessFiles
TCPUserAccessFilesSets the access files to useTCPUserAccessFilesDefault
none
Context
server config, <VirtualHost>, <Global>
Module
mod_wrap
Compatibility
1.2.1 and later
Description
TCPUserAccessFiles allows for access control files, the same types of
files required by TCPAccessFiles, to be applied to select users. The given
user-expression is a logical AND expression. Listing multiple users in
a user-expression does not make much sense; however, this type of AND
evaluation allows for expressions such as "everyone except this user"
with the use of the ! negation prefix.
The rules for the filename paths are the same as for TCPAccessFiles settings.
See also
TCPAccessFiles,
TCPGroupAccessFiles
Examples
# user admin might be allowed to connect from anywhere
TCPUserAccessFiles admin /etc/ftpd-anywhere.allow /etc/ftpd-anywhere.deny
# while every other user has to connect from LAN addresses
TCPUserAccessFiles !admin /etc/ftpd-lan.allow /etc/ftpd-lan.deny
mod_core
TimeoutIdle
TimeoutIdle
TimeoutIdleSets the idle connection timeoutTimeoutIdleDefault
TimeoutIdle 600
Context
server config
Module
mod_core
Compatibility
0.99.0 and later
Description
The TimeoutIdle directive configures the maximum number of seconds that proftpd
will allow clients to stay connected without receiving any data on either
the control or data connection. If data is received on either connection,
the idle timer is reset. Setting TimeoutIdle to 0 disables the idle timer
completely (clients can stay connected for ever, without sending data). This
is generally a bad idea as a "hung" tcp connection which is never
properly disconnected (the remote network may have become disconnected from
the Internet, etc) will cause a child server to never exit (at least not for
a considerable period of time) until manually killed
See Also: TimeoutLogin, TimeoutNoTransferSee alsoExamples
mod_core
TimeoutLogin
TimeoutLogin
TimeoutLoginSets the login timeoutTimeoutLoginDefault
TimeoutLogin 300
Context
server config
Module
mod_core
Compatibility
0.99.0 and later
Description
The TimeoutLogin directive configures the maximum number of seconds a client
is allowed to spend authenticating. The login timer is not reset when a client
transmits data, and is only removed once a client has transmitted an acceptable
USER/PASS command combination.
See Also: TimeoutIdle, TimeoutNoTransferSee alsoExamples
mod_core
TimeoutNoTransfer
TimeoutNoTransfer
TimeoutNoTransferSets the connection without transfer timeoutTimeoutNoTransferDefault
TimeoutNoTransfer 300
Context
server config
Module
mod_core
Compatibility
0.99.0 and later
Description
The TimeoutNoTransfer directive configures the maximum number of seconds
a client is allowed to spend connected, after authentication, without issuing
a command which results in creating an active or passive data connection (i.e.
sending/receiving a file, or receiving a directory listing).
See Also: TimeoutIdle, TimeoutLoginSee alsoExamples
mod_core
TimeoutStalled
TimeoutStalled
TimeoutStalledSets the timeout on stalled downloadsTimeoutStalledDefault
TimeoutStalled 3600
Context
server config
Module
mod_core
Compatibility
1.1.6 and later
Description
The TimeoutStalled directive sets the maximum number of seconds a data connection
between the proftpd server and an FTP client can exist but have no actual
data transferred (i.e. "stalled"). If the seconds
argument is set to 0, data transfers are allowed to stall
indefinitely.See alsoExamples
mod_core
TimesGMT
TimesGMT
TimesGMTToggle time display between GMT and localTimesGMTDefault
(versions 1.2.0pre9 and beyond) on
Context
server config, <VirtualHost>, <Anonymous>, <Global>
Module
mod_core
CompatibilityDescription
Compatibility: 1.2.0pre9 and later
The TimesGMT option causes the server to report all ls and MDTM times in
GMT and not local time.See alsoExamples
mod_core
TransferLog
TransferLog
TransferLogSpecify the path to the transfer logTransferLogDefault
TransferLog /var/log/xferlog
Context
server config, <Anonymous>, <VirtualHost>, <Global>
Module
mod_core
Compatibility
1.1.4 and later
Description
The TransferLog directive configures the full path to the "wu-ftpd style"
file transfer log. Separate log files can be created for each Anonymous
and/or VirtualHost.
Additionally, the special keyword NONE can be used,
which disables wu-ftpd style transfer logging for the context in which the
directive is used (only applicable to version 1.1.7 and later).
See Also: ExtendedLog, LogFormatSee alsoExamples
mod_core
Umask
Umask
UmaskSet the default UmaskUmaskDefault
None
Context
server config, <Anonymous>, <VirtualHost>, <Directory>, <Global>, .ftpaccess
Module
mod_core
Compatibility
0.99.0 and later
DescriptionUmask sets the mask applied to newly created file and directory
permissions within a given context. By default, the Umask in the server
configuration, <VirtualHost> or <Anonymous> block is used,
unless overridden by a "per-directory" Umask setting. Any
arguments supplied must be an octal number, in the format 0xxx. An
optional second argument can specify a Umask to be used when creating
directories. If a second argument isn't specified, directories are created
using the default Umask in the first argument. For more information on
umasks, consult your operating system documentation/man pages.Proftpd will not create files that have the execution bit turned
on, this is a security driven design decision. The permissions of the
uploaded file can be changed by issuing a SITE CHMOD command can be
used to change the mode of the uploaded file. Syntax of the command is:
SITE CHMOD <mode> <file>.See alsoExamples
mod_core
UseFtpUsers
UseFtpUsers
UseFtpUsersBlock based on /etc/ftpusersUseFtpUsersDefault
UseFtpUsers on
Context
server config, <Anonymous>, <VirtualHost>, <Global>
Module
mod_core
Compatibility
0.99.0 and later
Description
Legacy FTP servers generally check a special authorization file (typically
/etc/ftpusers) when a client attempts to authenticate. If the user's name
is found in this file, FTP access is denied. For compatibility sake, proftpd
defaults to checking this file during authentication. This behavior can be
suppressed using the UseFtpUsers configuration directive.See alsoExamples
mod_ls
UseGlobbing
UseGlobbing
UseGlobbingToggles use of glob() functionalityUseGlobbingDefault
UseGlobbing on
Context
server config, <VirtualHost>, <Global>, <Anonymous>
Module
mod_ls
Compatibility
1.2.5rc1 and later
Description
The UseGlobbing directive controls use of glob() functionality, which is
needed for supporting wildcard characters such as *.See also
mod_core
User
User
UserSet the user the daemon will run asUserDefault
None
Context
server config, <VirtualHost>, <Anonymous>, <Global>
Module
mod_core
Compatibility
0.99.0 and later
Description
The User directive configures which user the proftpd daemon will normally
run as. By default, proftpd runs as root which is considered undesirable
in all but the most trustful network configurations. The User directive used
in conjunction with the Group directive
instructs the daemon to switch to the specified user and group as quickly
as possible after startup. On some unix variants, the daemon will occasionally
switch back to root in order to accomplish a task which requires super-user
access. Once the task is completed, root privileges are relinquished and the
server continues to run as the specified user and group. When applied to a
<VirtualServer> block, proftpd
will run as the specified user/group on connections destined for the virtual
server's address or port. If either User or Group
is applied to an <Anonymous>
block, proftpd will establish an anonymous login when a user attempts to login
with the specified userid, as well as permanently switching to the corresponding
uid/gid (matching the User/Group parameters found in the anonymous block)
after login.
Note: When an authorized unix user is authenticated and logs in, all former
privileges are released, the daemon switches permanently to the logged in
user's uid/gid, and is never again capable of switching back to root or any
other user/group.See alsoExamples
mod_auth
UserAlias
UserAlias
UserAliasAlias a username to a system userUserAliasDefault
None
Context
server config, <VirtualHost>, <Anonymous>, <Global>
Module
mod_auth
Compatibility
0.99.0 and later
Description
ProFTPD requires a real username/uid when authenticating users as
provided by PAM, AuthUserFile or another authentication mechanism.
There are however times when additional aliases are required but it is
undesirable to provide additional login accounts.UserAlias provides a mechanism to do this, a typical and common
example is within Anonymous configuration blocks. It is normal for the
server to use 'ftp' as the primary authentication user, however it is
common practice for users to login using "anonymous". This is achieved
by adding the following to the config file.See alsoExamples
UserAlias anonymous ftp
mod_auth
UserDirRoot
UserDirRoot
UserDirRootSet the chroot directory to a subdirectory of the anonymous serverUserDirRootDefault
off
Context
<Anonymous>
Module
mod_auth
Compatibility
1.2.0pre2 and later
Description
When set to true, the chroot base directory becomes a subdirectory of the
anonymous ftp directory, based on the username of the current user. For
example, assuming user "foo" is aliased to "ftp", logging in as "foo" causes
proftpd to run as real user ftp, but to chroot into ~ftp/foo
instead of just ~ftp.See alsoExamples
mod_core
UseReverseDNS
UseReverseDNS
UseReverseDNSToggle rDNS lookupsUseReverseDNSDefault
UseReverseDNS on
Context
server config
Module
mod_core
Compatibility
1.1.7 and later
Description
Normally, incoming active mode data connections and outgoing passive mode
data connections have a reverse DNS lookup performed on the remote host's
IP address. In a chroot environment (such as <Anonymous>
or DefaultRoot), the /etc/hosts file cannot be
checked and the only possible resolution is via DNS. If for some reason, DNS
is not available or improperly configured this can result in proftpd blocking
("stalling") until the libc resolver code times out. Disabling this
directive prevents proftpd from attempting to reverse-lookup data connection
IP addresses. See alsoExamples
mod_core
UserOwner
UserOwner
UserOwnerSet the user ownership of new files / directoriesUserOwnerDefault
None
Context
<Anonymous>, <Directory>
Module
mod_core
Compatibility
1.2pre11 and later
Description
The UserOwner directive configures which user all newly created directories
and files will be owned by, within the context that UserOwner is applied to.
The user ID of username cannot be 0 (root).
Where it is used, the GroupOwner directive is not
restricted to groups that the current user is a member of.See alsoExamples
mod_core
UserPassword
UserPassword
UserPasswordCreates a hardcoded username/password pairUserPasswordDefault
None
Context
server config, <VirtualHost>, <Anonymous>, <Global>
Module
mod_core
Compatibility
0.99.0pl5 and later
Description
The UserPassword directive creates a password for a particular user which
overrides the user's normal password in /etc/passwd (or /etc/shadow). The
override is only effective inside the context to which UserPassword is applied.
The hashed-password argument is a cleartext string
which has been passed through the standard unix crypt() function. Do
NOT use a cleartext password. This can be useful when combined with
UserAlias to provide multiple logins to an Anonymous FTP site.
See Also: GroupPasswordSee alsoExamples
mod_ratio
UserRatio
UserRatio
UserRatioRatio directiveUserRatioDefault
None known
Context
<Directory>, <Anonymous>, <Limit>,.ftpaccess
Module
mod_ratio
Compatibility
at least 1.2.0 and later
Description
The UserRatio directive ....
Example:
UserRatioSee alsoExamples
mod_core
VirtualHost
VirtualHost
VirtualHostDefine a virtual ftp serverVirtualHostDefault
None
Context
server config
Module
mod_core
Compatibility
0.99.0 and later
Description
The VirtualHost configuration block is used to create an independent set
of configuration directives that apply to a particular hostname or IP address.
It is often used in conjunction with system level IP aliasing or dummy network
interfaces in order to establish one or more "virtual" servers which
all run on the same physical machine. The block is terminated with a </VirtualHost>
directive. By utilizing the
Port directive inside a VirtualHost block, it is
possible to create a virtual server which uses the same address as the master
server, but listens on a separate tcp port (incompatible with ServerType inetd).
When proftpd starts, virtual server connections are handled in one of two
ways, depending on the
ServerType setting:
inetd
The daemon examines the destination address and port of the incoming connection
handed off from inetd. If the connection matches one of the configured virtual
hosts, the connection is serviced based on the appropriate configuration.
If no virtual host matches, and the main server does not match, the client
is informed that no server is available to service their requests and disconnected.
standalone
After parsing the configuration file, the daemon begins listening for connections
on all configured ports, spawning child processes as necessary to handle
connections for either the main server or any virtual servers.
Because of the method that the daemon uses to listen for connections when
in standalone mode, it is possible to support an
exceedingly large number of virtual servers, potentially exceeding the number
of per-process file descriptors. This is due to the fact that a single file
descriptor is used to listen to each configured port, regardless of the number
of addresses being monitored. Note that it may be necessary to increase
the
tcpBackLog value on heavily loaded
servers in order to avoid kernel rejected client connections ("Connection
refused").See alsoExamples
mod_core
WtmpLog
WtmpLog
WtmpLogToggle logging to wtmpWtmpLogDefault
WtmpLog on
Context
server config, <VirtualHost>, <Anonymous>, <Global>
Module
mod_core
Compatibility
1.1.7 and later
Description
The WtmpLog directive controls proftpd's logging of ftp
connections to the host system's wtmp file (used by such commands as
`last'). By default, all connections are logged via wtmp.
Please report any corrections or additions via http://bugs.proftpd.net/ See alsoExamples