Difference between revisions of "Whitelist"

From Fail2ban
Jump to: navigation, search
(New page: Whitelisting Whitelisting of a single host for, lets say, courier-auth is NOT possible! and thats very bad ... and the README / Howto to whitelisting is very poor - and thats even worse ...)
 
Line 1: Line 1:
Whitelisting  
+
'''Whitelisting'''
  
 
Whitelisting of a single host for, lets say, courier-auth is NOT possible! and thats very bad ... and the README / Howto to whitelisting is very poor - and thats even worse ...
 
Whitelisting of a single host for, lets say, courier-auth is NOT possible! and thats very bad ... and the README / Howto to whitelisting is very poor - and thats even worse ...
 +
 +
The serversystem is Debian Etch, fail2ban according to apt-cache show:
 +
 +
  
 
I tried it with:
 
I tried it with:

Revision as of 21:08, 1 April 2010

Whitelisting

Whitelisting of a single host for, lets say, courier-auth is NOT possible! and thats very bad ... and the README / Howto to whitelisting is very poor - and thats even worse ...

The serversystem is Debian Etch, fail2ban according to apt-cache show:


I tried it with:

1) /etc/fail2ban/jail.conf:

[DEFAULT]

ignoreip = 127.0.0.1, 82.198.214.113

= no success

global_whitelist = /etc/fail2ban/whitelist.txt

= no success


2) /etc/fail2ban/jail.local:

[DEFAULT]

ignoreip = 127.0.0.1, 82.198.214.113

= no success

3) /etc/fail2ban/fai2ban.conf:

[Definition]

ignoreip = 127.0.0.1, 82.198.214.113

= no success

Finally, I tried to set a "ignoreip"-Line in /etc/filter.d/courierauth, but with no success :-(

As far as I can see, there is no simple solution to whitelist single hosts (or networks?).


At the moment, we have de-activated fai2ban on our mailserver.


Greetings


Lars Behrens