fail2ban

Author	SHA1	Message	Date
Yaroslav Halchenko	bbb9e6f094	* NEWS.Debian confusions - the latest NEWS entry and postinst message were rephrased (Closes: #402350)	18 years ago
Yaroslav Halchenko	f4015e0c3c	forgotten fi	18 years ago
Yaroslav Halchenko	28dad3752c	* Warning NEWS entry for 0.7.1 was not shown during installation on test boxes, thus postinst was adjusted accordingly to inform the user about the changes in the configuration files since 0.6.	18 years ago
Yaroslav Halchenko	73f0ed8976	changed ownership of all existing logs	19 years ago
Yaroslav Halchenko	b00161f7ec	fixed #352053	19 years ago
Yaroslav Halchenko	a40245010f	* Fixed typos (thanx to Ross Boylan). * Robust startup: if iptables module gets fully initialized after startup of fail2ban, fail2ban will do "maxreinit" attempts to initialize its own firewall. It will sleep between attempts for "polltime" number of seconds (closes: #334272). * To overcome possible conflict with other firewall solutions and as a secondary solution for the bug 334272, fail2ban startup is moved during bootup to the latest (S99) sequenece position. That should not cause any discomfort I believe.	19 years ago
Yaroslav Halchenko	501955f36a	adjusted README: removed part about missing chain because the issue is	19 years ago
Yaroslav Halchenko	555d12ece4	added a notification regarding configuration file	19 years ago
Yaroslav Halchenko	fc4531ff45	fixed security hole with world-open umask	20 years ago