Changeset 17876 for src/router/proftpd/doc/contrib/mod_ban.html
- Timestamp:
- 11/11/11 13:17:43 (19 months ago)
- File:
-
- 1 edited
-
src/router/proftpd/doc/contrib/mod_ban.html (modified) (12 diffs)
Legend:
- Unmodified
- Added
- Removed
-
src/router/proftpd/doc/contrib/mod_ban.html
r14672 r17876 1 <!-- $Id: mod_ban.html,v 1. 8 2009/12/08 00:24:42castaglia Exp $ -->1 <!-- $Id: mod_ban.html,v 1.12 2011/02/20 02:21:50 castaglia Exp $ --> 2 2 <!-- $Source: /cvsroot/proftp/proftpd/doc/contrib/mod_ban.html,v $ --> 3 3 … … 41 41 <h2>Directives</h2> 42 42 <ul> 43 <li><a href="#BanCache">BanCache</a> 44 <li><a href="#BanCacheOptions">BanCacheOptions</a> 43 45 <li><a href="#BanControlsACLs">BanControlsACLs</a> 44 46 <li><a href="#BanEngine">BanEngine</a> … … 54 56 <li><a href="#permit"><code>permit</code></a> 55 57 </ul> 58 59 <p> 60 <hr> 61 <h3><a name="BanCache">BanCache</a></h3> 62 <strong>Syntax:</strong> BanCache <em>driver</em><br> 63 <strong>Default:</strong> None<br> 64 <strong>Context:</strong> server config, <code><VirtualHost></code>, <code><Global></code><br> 65 <strong>Module:</strong> mod_ban<br> 66 <strong>Compatibility:</strong> 1.3.4rc2 and later 67 68 <p> 69 <hr> 70 <h3><a name="BanCacheOptions">BanCacheOptions</a></h3> 71 <strong>Syntax:</strong> BanCacheOptions <em>opt1 ... optN</em><br> 72 <strong>Default:</strong> None<br> 73 <strong>Context:</strong> server config, <code><VirtualHost></code>, <code><Global></code><br> 74 <strong>Module:</strong> mod_ban<br> 75 <strong>Compatibility:</strong> 1.3.4rc2 and later 56 76 57 77 <p> … … 169 189 MaxClientsPerHost 170 190 MaxClientsPerUser 191 MaxCommandRate 171 192 MaxConnectionsPerHost 172 193 MaxHostsPerUser … … 175 196 TimeoutLogin 176 197 TimeoutNoTransfer 198 UnhandledCommand 177 199 </pre> 178 200 An event is generated whenever one of these limits is reached by a client. … … 188 210 time interval, then a ban is automatically added. The IP address of 189 211 the connecting client is banned when the following event rules are 190 triggered: <code>AnonRejectPasswords</code>, <code>MaxClientsPerHost</code>, 191 <code>MaxConnectionsPerHost</code>, <code>MaxLoginAttempts</code>, 192 <code>TimeoutIdle</code>, and <code>TimeoutNoTransfer</code>. The class of 193 the connected client, if any, is banned when a rule for 212 triggered: <code>AnonRejectPasswords</code>, <code>MaxCommandRate</code>, 213 <code>MaxClientsPerHost</code>, <code>MaxConnectionsPerHost</code>, 214 <code>MaxLoginAttempts</code>, <code>TimeoutIdle</code>, 215 <code>TimeoutNoTransfer</code>, and <code>UnhandledCommand</code>. The class 216 of the connected client, if any, is banned when a rule for 194 217 <code>MaxClientsPerClass</code> is triggered. Rules for 195 218 <code>MaxClientsPerUser</code> and <code>MaxHostsPerUser</code> will cause … … 254 277 <hr> 255 278 <h3><a name="ban"><code>ban</code></a></h3> 256 <strong>Syntax:</strong> ftpdctl ban <em>class|host|info|user name1 [name2 ...]</em><br>279 <strong>Syntax:</strong> ftpdctl ban <em>class|host|info|user [-s address#port] name1 [name2 ...]</em><br> 257 280 <strong>Purpose:</strong> Add a ban or display ban information<br> 258 281 … … 263 286 ftpdctl ban user dave 264 287 </pre> 288 This will create a ban rule for user 'dave' for <i>all</i> virtual servers in 289 your <code>proftpd.conf</code>. If you want to create such a ban rule, but 290 only for one specific <code><VirtualHost></code>, use the <code>-s</code> 291 command-line option, <i>e.g.</i>: 292 <pre> 293 ftpdctl ban user -s 1.2.3.4#21 dave 294 </pre> 295 This example will create the user 'dave' ban rule for the 296 <code><VirtualHost></code> handling IP address 1.2.3.4, port 21. 297 The <code>-s</code> command-line option applies to <em>host</em> and 298 <em>class</em> bans as well. 299 300 <p> 265 301 To ban specific hosts, you can use either IP addresses or DNS names: 266 302 <pre> … … 288 324 ftpdctl: Reason: MaxLoginAttempts autoban at Wed May 19 14:59:25 2004 289 325 ftpdctl: Expires: Wed May 19 14:59:55 2004 (in 24 seconds) 326 ftpdctl: <VirtualHost> <i>ServerName</i> (1.2.3.4#21) 290 327 </pre> 291 328 It is also possible to see the state of ban event rules, using the … … 313 350 <hr> 314 351 <h3><a name="permit"><code>permit</code></a></h3> 315 <strong>Syntax:</strong> ftpdctl permit <em>class|host|user name1 [name2 ...]</em><br>352 <strong>Syntax:</strong> ftpdctl permit <em>class|host|user [-s address#port] name1 [name2 ...]</em><br> 316 353 <strong>Purpose:</strong> Permit banned clients to connect<br> 317 354 … … 320 357 and classes: 321 358 <pre> 322 ftpdctl permit user dave 323 ftpdctl permit host 1.2.3.4 gw.evil.com 324 ftpdctl permit class anonftp 359 # ftpdctl permit user dave 360 # ftpdctl permit user -s 1.2.3.4#21 dave 361 # ftpdctl permit host 1.2.3.4 gw.evil.com 362 # ftpdctl permit class anonftp 325 363 </pre> 326 364 … … 455 493 456 494 Author: <i>$Author: castaglia $</i><br> 457 Last Updated: <i>$Date: 20 09/12/08 00:24:42$</i><br>495 Last Updated: <i>$Date: 2011/02/20 02:21:50 $</i><br> 458 496 459 497 <br><hr> 460 498 461 499 <font size=2><b><i> 462 © Copyright 2004-20 09TJ Saunders<br>500 © Copyright 2004-2011 TJ Saunders<br> 463 501 All Rights Reserved<br> 464 502 </i></b></font>
Note: See TracChangeset
for help on using the changeset viewer.
