maybe you dist-upgraded from an earlier version where it used to be as
/etc/fail2ban.conf. /usr/share/doc/fail2ban/README.Debian.gz probably
has what you are looking for:
Upgrade from 0.6 versions:
-
* New Config Files Format:
If you had introduced your own sections in
fail2ban doesn't read /etc/fail2ban.conf at all. The default
fail2ban.conf only configures loglevel, logtarget and the socket path,
so if you don't read the manual how to configure the jails (in
fail2ban.jail) then I'm not sure how it can be a bug.
** Changed in: fail2ban (Ubuntu)
Status:
The dpkg -L fail2ban gives me /etc/fail2ban.conf on Ubuntu 8.04.1.
If a configuration file is shipped with a package but not used by that
package, then it's a bug. fail2ban.jail doesn't exist on my system,
/etc/fail2ban/jail.conf does. It can list all sorts of information, but
that's worthless if
This is what I have:
syb...@zebra:~$ apt-cache show fail2ban
Package: fail2ban
Priority: optional
Section: universe/net
Installed-Size: 600
Maintainer: Ubuntu MOTU Developers ubuntu-m...@lists.ubuntu.com
Original-Maintainer: Yaroslav Halchenko deb...@onerussian.com
Architecture: all
Version:
dpkg -L on hardy doesn't list /etc/fail2ban.conf here. Don't know where
you got it.
The information in fail2ban.conf is not contradicting, the default files
have nothing in common (fail2ban.conf and jail.conf), and surely users
need to read the manual before trying to configure something like
** Summary changed:
- configuration ambiguous
+ fail2ban configuration ambiguous
--
fail2ban configuration ambiguous
https://bugs.launchpad.net/bugs/267087
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
