Enhanced PHP File Manager

⬆️ Go Up (..)

📊 Server Information

Server:

nginx/1.28.0

System:

Linux 6.8.0-90-generic

PHP Version:

8.4.15

User:

alqudsvolunteers

Directory:

/home/alqudsvolunteers/rootlink/usr/share/doc/proftpd-doc/contrib

Free Space:

81.59 GB

🔧 Quick Actions

✏️ Editing: mod_wrap.html

<!DOCTYPE html>
<html>
<head>
<title>ProFTPD module mod_wrap</title>
</head>

<hr>
<center>
<h2>ProFTPD module <code>mod_wrap</code></h2>
</center>
<hr>

This module is contained in the <code>contrib/mod_wrap.c</code> file for
ProFTPD 1.2.x, and is not compiled by default. It enables the daemon to
use the common tcpwrappers access control library while in
<code>standalone</code> mode, and in a very configurable manner.

If not installed on your system, the TCP wrappers library, required by this
module, can be found
<a href="ftp://ftp.porcupine.org/pub/security/tcp_wrappers_7.6.tar.gz">here</a>,
on Wietse Venema's site. Once installed, it highly recommended
that the <code>hosts_access(3)</code> and <code>hosts_access(5)</code> man
pages be read and understood. The <a href="#Installation">installation</a>
of <code>mod_wrap</code> is fairly straightforward, with some caveats for
Solaris and FreeBSD users.

Many programs will automatically add entries in the common allow/deny files,
and use of this module will allow a ProFTPD daemon running in
<code>standalone</code> mode to adapt as these entries are added. The
<code>portsentry</code> program does this, for example: when illegal access
is attempted, it will add hosts to the <code>/etc/hosts.deny</code> file.

The most current version of <code>mod_wrap</code> is distributed with the
ProFTPD source code.

<h2>Author</h2>

Please contact TJ Saunders &lt;tj at castaglia.org&gt; with any
questions, concerns, or suggestions regarding this module.

<h2>Thanks</h2>

2000-05-29: Thanks to David Douthitt &lt;ssrat at mailbag.com&gt;
for pointing out the usefulness of using <code>mod_wrap</code> in conjunction
with <code>portsentry</code>

2001-03-01: Updated the configuration directives, as per
lung at theuw.net's helpful suggestions.
 

2001-09-24: Thanks to Zenon Mousmoulas &lt;cajoline at
chaosengine.de &gt; for helping determine that adding <code>-lnsl</code> would
help in compiling <code>mod_wrap</code> with the stock RedHat
<code>libwrap.a</code>, so that recompiling tcpwrappers without NIS/YP support
should no longer be necessary.

2001-09-27: Thanks to Gabe Frost &lt;gfrost at gostnet.com&gt;
for helping track down several mergedown bugs.

2001-12-19: Thanks to Mark Castillo &lt;markc at webFreak.com&gt;
for pointing out the issue with passwords not being properly hidden

<h2>Directives</h2>
<ul>
 <li><a href="#TCPAccessFiles">TCPAccessFiles</a>
 <li><a href="#TCPAccessSyslogLevels">TCPAccessSyslogLevels</a>
 <li><a href="#TCPGroupAccessFiles">TCPGroupAccessFiles</a>
 <li><a href="#TCPServiceName">TCPServiceName</a>
 <li><a href="#TCPUserAccessFiles">TCPUserAccessFiles</a>
</ul>

<hr>
<h3><a name="TCPAccessFiles">TCPAccessFiles</a></h3>
Syntax: TCPAccessFiles allow-filename deny-filename 
Default: None 
Context: server config, <code>&lt;VirtualHost</code>, <code>&lt;Global&gt;</code>, <code>&lt;Anonymous&gt;</code> 
Module: mod_wrap 
Compatibility: 1.2.1 and later

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 <code>~/</code>, 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 <code>~user/</code>, where user is some system user. In this latter case,
<code>mod_wrap</code> will attempt to resolve and verify the given user's home
directory on start-up.

The service name for which <code>mod_wrap</code> will look in the indicated
access files is <code>proftpd</code> by default; this can be configured via
the <code>TCPServiceName</code> directive.

There is a built-in precedence to the <code>TCPAccessFiles</code>,
<code>TCPGroupAccessFiles</code>, and <code>TCPUserAccessFiles</code>
directives, if all are used. <code>mod_wrap</code> will look for applicable
<code>TCPUserAccessFiles</code> for the connecting user first. If no applicable
<code>TCPUserAccessFiles</code> is found, <code>mod_wrap</code> will search for
<code>TCPGroupAccessFiles</code> which pertain to the connecting user. If not
found, <code>mod_wrap</code> will then look for the server-wide
<code>TCPAccessFiles</code> 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.

Example:
<pre>
 # 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
</pre>

See also:
 <a href="#TCPGroupAccessFiles">TCPGroupAccessFiles</a>,
 <a href="#TCPServiceName">TCPServiceName</a>,
 <a href="#TCPUserAccessFiles">TCPUserAccessFiles</a>

<hr>
<h3><a name="TCPAccessSyslogLevels">TCPAccessSyslogLevels</a></h3>
Syntax: TCPAccessSyslogLevels allow-level deny-level 
Default: <code>TCPAccessSyslogLevels info warn</code> 
Context: server config, <code>&lt;VirtualHost&gt;</code>, <code>&lt;Global&gt;</code>, <code>&lt;Anonymous&gt;</code> 
Module: mod_wrap 
Compatibility: 1.2.1 and later

ProFTPD can log when a connection is allowed, or denied, as the result of rules
in the files specified in <code>TCPAccessFiles</code>, to the Unix
<code>syslog</code> mechanism. A discussion on the <code>syslog</code> levels
which can be used is given in the <code>SyslogLevel</code> 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.

Example:
<pre>
 TCPAccessSyslogLevels debug warn
</pre>

<hr>
<h3><a name="#TCPGroupAccessFiles">TCPGroupAccessFiles</a></h3>
Syntax: TCPGroupAccessFiles group-expression allow-filename deny-filename 
Default: None 
Context: server config, <code>&lt;VirtualHost&gt;</code>, <code>&lt;Global&gt;</code> 
Module: mod_wrap 
Compatibility: 1.2.1 and later

<code>TCPGroupAccessFiles</code> allows for access control files, the same
types of files required by <code>TCPAccessFiles</code>, 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
<code>!</code> prefix.

The rules for the filename paths are the same as for
<code>TCPAccessFiles</code> settings.

Example:
<pre>
 # 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
</pre>

See Also: <a href="#TCPAccessFiles">TCPAccessFiles</a>

<hr>
<h3><a name="TCPServiceName">TCPServiceName</a></h3>
Syntax: TCPServiceName name 
Default: <code>TCPServiceName proftpd</code> 
Context: server config, <code>&lt;VirtualHost&gt;</code>, <code>&lt;Global&gt;</code> 
Module: mod_wrap 
Compatibility: 1.2.1 and later

<code>TCPServiceName</code> is used to configure the name of the service under
which <code>mod_wrap</code> will check the allow/deny files. By default, this
is the name of the program started, i.e. &quot;proftpd&quot;. However,
some administrators may want to use a different, more generic service name,
such as &quot;ftpd&quot;; use this directive for such needs.

<hr>
<h3><a name="TCPUserAccessFiles">TCPUserAccessFiles</a></h3>
Syntax: TCPUserAccessFiles user-expression allow-filename deny-filename 
Default: None 
Context: server config, <code>&lt;VirtualHost&gt;</code>, <code>&lt;Global&gt;</code> 
Module: mod_wrap 
Compatibility: 1.2.1 and later

<code>TCPUserAccessFiles</code> allows for access control files, the same types
of files required by <code>TCPAccessFiles</code>, 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 &quot;everyone
except this user&quot; with the use of the <code>!</code> negation
prefix.

The rules for the filename paths are the same as for
<code>TCPAccessFiles</code> settings.

Example:
<pre>
 # 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
</pre>

See also: <a href="#TCPAccessFiles">TCPAccessFiles</a>

Question: Using <code>mod_wrap</code>, connections
from hosts that have broken reverse DNS mappings are refused. OpenSSH
uses the same <code>libwrap</code> library, and this doesn't happen. Is it
a bug in <code>mod_wrap</code>? 
Answer: No, it is not, strictly speaking, a bug
in <code>mod_wrap</code>.

Users who encounter this issue will usually find log messages that look
like the any/all of the following in their syslog:
<pre>
 proftpd: warning: can't verify hostname: gethostbyname(dns-name) failed
 proftpd: warning: can't verify hostname: getaddrinfo(anothername.net, AF_INET) failed
 proftpd: warning: host name/name mismatch: somedomain.com != vs-23.somename.com
</pre>
These log messages do not, in fact, come from <code>proftpd</code>.
Instead, they come from the <code>libwrap</code> library, which is used by
the <code>mod_wrap</code> module. In particular, the <code>libwrap</code>
library emits these log messages when it has been compiled with the
<code>-DPARANOID</code> compile-time option (and most installations of the
<code>libwrap</code> library are compiled this way).

OpenSSH allows such connections because the OpenSSH code, when using the
<code>libwrap</code> library, does not check for paranoid/unknown results
from the <code>host_access()</code> function of the <code>libwrap</code>
library. The <code>mod_wrap</code> module for ProFTPD does check
for these values, thus why those connections are refused by
<code>mod_wrap</code> but not OpenSSH. This just demonstrates that not all
applications use the <code>libwrap</code> library the same way.

The solution, in most cases, is to switch to using the newer
<a href="mod_wrap2.html"><code>mod_wrap2</code></a> module, which does
not use the <code>libwrap</code> library (and thus does not encounter
this issue).

<hr>
<h2><a name="Installation">Installation</a></h2>
Use of <code>mod_wrap</code> is straightforward, with some minor caveats. If
you're using Solaris, you'll need to obtain and build the tcpwrappers library,
as this library does not come installed on stock Solaris systems. If you're
using FreeBSD or Mac OSX (and possibly other versions), you'll need to change
the following line in the header of <code>mod_wrap.c</code>:
<pre>
 * $Libraries: -lwrap -lnsl$
</pre>
to be:
<pre>
 * $Libraries: -lwrap$
</pre>
This line is needed on Linux and Solaris machines, to properly link against
the <code>libnsl.a</code> library, which implements the NIS/YP functions.
In FreeBSD and Mac OSX, these functions are implemented in <code>libc</code>.

Then, you need simply follow the normal steps for using third-party modules in
ProFTPD:
<pre>
 $ ./configure --with-modules=mod_wrap
 $ make
 $ make install
</pre>

</body>
</html>

❌ Cancel

🗂️ Enhanced PHP File Manager

📊 Server Information

🔧 Quick Actions

✏️ Editing: mod_wrap.html

📤 Upload File

📁 Create Folder

📄 Create File

✏️ Rename Item

🗑️ Delete Confirmation