File: README.classes

package info (click to toggle)
proftpd-dfsg 1.3.0-19etch3
  • links: PTS
  • area: main
  • in suites: etch
  • size: 9,604 kB
  • ctags: 5,598
  • sloc: ansic: 59,475; sh: 18,832; perl: 1,474; makefile: 1,191
file content (39 lines) | stat: -rw-r--r-- 1,162 bytes parent folder | download | duplicates (2)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39

Classes
-------

In versions of ProFTPD prior to 1.2.10rc1, a proftpd.conf that used Classes
might look like:

  ...

  Classes on
  Class foo ip 127.0.0.1
  Class foo regex *.evil.com
  Class foo limit 10

  ...
 
The new Class code uses <Class> sections.  The above configuration would
thus be:

  <Class foo>
    From 127.0.0.1
    From *.evil.com
  </Class>

The Class and Classes configuration directives are deprecated.  The new
<Class> sections do not support the old "limit" keyword.  Instead,
a new MaxClientsPerClass configuration directive can be used:

  MaxClientsPerClass foo 10

There is no equivalent for the old "Class" directive.  The proftpd engine
will always try to determine if the connecting client belongs to a defined
class.  No class definitions means that classes will not be used.

Classes can only be defined in the "server config" context, not on a <Global>
or per-<VirtualHost> basis.  This is because the class for a client is
determined as soon as the client connects to the server, before the server
determines which <VirtualHost> the client is trying to reach.  Therefore,
class definitions always apply to the entire server.