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.64 GB

🔧 Quick Actions

✏️ Editing: mod_wrap2_redis.html

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

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

This submodule provides the Redis server &quot;driver&quot; for storing
IP/DNS-based access control information in Redis lists/sets.

This <code>mod_wrap2</code> submodule is contained in the
<code>mod_wrap2_redis.c</code> file, and is not compiled by default. See the
<code>mod_wrap2</code> <a href="mod_wrap2.html#Installation">installation</a>
instructions.

<h2>Author</h2>

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

<hr><h2><a name="RedisListsSets">Redis Access Lists/Sets</a></h2>
The <code>mod_wrap2_redis</code> module supports the &quot;redis&quot; string
for the source-type parameter of the
<a href="mod_wrap2.html#WrapUserTables"><code>WrapUserTables</code></a>,
<a href="mod_wrap2.html#WrapGroupTables"><code>WrapGroupTables</code></a>,
and
<a href="mod_wrap2.html#WrapTables"><code>WrapTables</code></a>,
configuration directives. If the &quot;redis&quot; source-type is used,
then the source-info parameter must be as described below. Note
that support for Redis-based lists/sets requires the use of
<code>mod_redis</code> (e.g. via the <code>--enable-redis</code>
configure option).

<code>mod_wrap2_redis</code> requires only that the
<a href="../modules/mod_redis.html"><code>mod_redis</code></a> module be
enabled and configured to access a Redis server.

One Redis list (or set) is needed to retrieving access information from the
allow "table", and another list/set for access information from the
deny "table". These lists/sets should contain a list of words,
where each word is a host name, host address, pattern, or wildcard (see
<a href="mod_wrap2.html#AccessRules">here</a> for how these things are
defined).

Optionally, other Redis lists/sets can be defined to look up access
<a href="mod_wrap2.html#AccessOptions">options</a> from the allow and
deny tables.

For Redis lists, the format for the <code>WrapUserTables</code>,
<code>WrapGroupTables</code>, and <code>WrapTables</code> directives is:
<pre>
 WrapTables redis:/list:<code>allow-list-key</code>[/list:<code>allow-list-options-key</code>] \
 redis:list:<code>deny-list-key</code>[/list:<code>deny-list-options-key</code>]
</pre>
where the allow-list-options-key and deny-list-options-key
portions of the string are optional.

For Redis sets, the format is similar to the above, only you specify
a key prefix of "set:" rather than "list", e.g.:
<pre>
 WrapTables redis:/set:<code>allow-set-key</code>[/set:<code>allow-set-options-key</code>] \
 redis:set:<code>deny-set-key</code>[/set:<code>deny-set-options-key</code>]
</pre>

Redis Access Lists/Sets Example 
Here are example directives to help demonstrate how the <code>mod_redis</code>
hooks are used by <code>mod_wrap2_redis</code>.
These example directives assume the existence of two lists: a
<code>wrapallow</code> list that defines allowed clients, and a
<code>wrapdeny</code> list that defines the denied clients.

<pre>
 # Using Redis lists
 WrapTables redis:/list:wrapallow redis:/list:wrapdeny

# Using Redis sets
 WrapTables redis:/set:wrapallow redis:/set:wrapdeny
</pre>

For per-user/per-group lists/sets, the key name can use the <code>%{name}</code>
variable, like so:
<pre>
 WrapUserTables * redis:/list:wrapallow.%{name} redis:/list:wrapdeny.%{name}
 WrapGroupTables * redis:/list:wrapallow.%{name} redis:/list:wrapdeny.%{name}
</pre>
In the case of <code>WrapUserTables</code>, the <code>%{name}</code> variable
will be resolved to the user name (from the <code>USER</code> command) of the
logging-in user; for <code>WrapGroupTables</code>, <code>%{name}</code> will be
resolved to the name of the user's primary group.

If the administrator wants to make use of access options, then URIs for those
options would need to be similarly defined:
<pre>
 # Access tables for users (with options)
 WrapUserTables user1,user2 \
 redis:/list:allowed.%{name}/list:allowed-options.%{name} \
 redis:/list:denied.%{name}/list:denied-options.%{name}

# Access tables for groups (with options)
  WrapGroupTables group1,group2 \
    redis:/list:allowed.%{name}/list:allowed-options.%{name} \
    redis:/list:denied.%{name}/list:denied-options.%{name}

# Access tables for everyone else (without options)
 WrapTables redis:/list:allowed redis:/list:denied
</pre>

When constructing the client and options lists to return to
<code>mod_wrap2</code>'s access control engine, <code>mod_wrap2_redis</code>
will parse each returned item separately, handling both comma- and space-limited
names in an item, into client list items. This means that the administrator can
store multiple client and option tokens in multiple items, as in the above
schema, or the administrator can choose to store all of the clients and/or
options in a single item, in an appropriately formatted string.

</body>
</html>

❌ Cancel

🗂️ Enhanced PHP File Manager

📊 Server Information

🔧 Quick Actions

✏️ Editing: mod_wrap2_redis.html

📤 Upload File

📁 Create Folder

📄 Create File

✏️ Rename Item

🗑️ Delete Confirmation