#767119 handle /etc/fail2ban/jail.d/defaults-debian.conf differently

Package:
fail2ban
Source:
fail2ban
Submitter:
Christoph Anton Mitterer
Date:
2014-10-28 15:27:14 UTC
Severity:
wishlist
#767119#5
Date:
2014-10-28 15:06:45 UTC
From:
To:
Hi.

I really think it's a big improvement, that no jails are enabled per default
but since this changes the long standin behaviour of Debian's fail2ban
package, which had the sshd jail enabled per default, it should be added
to the NEWS.Debian entry.


Cheers,
Chris.

#767119#10
Date:
2014-10-28 15:11:04 UTC
From:
To:
Hi.

I just saw that this is now actually in:
/etc/fail2ban/jail.d/defaults-debian.conf

O:-)

Therefore closing.

Cheers,
Chris.

#767119#15
Date:
2014-10-28 15:22:03 UTC
From:
To:
reopen 767119
retitle 767119 handle /etc/fail2ban/jail.d/defaults-debian.conf differently
severity 767119 wishlist
stop

Hey again.

I think I can rededicate this bug for the following:

Wouldn't it be better if:
1) /etc/fail2ban/jail.d/defaults-debian.conf was not a conffile
2) named /etc/fail2ban/jail.d/ssh.conf instead and only created once on
upgrade from pre 0.9 versions
3) people be advised that in future they need to manually activate they
jails they want

(1) and (2) would have the advantage that one doesn't get another
conffile which one has to merge if the package default changes, and
"defaults-debian" is a IMHO not such an optimal name:
we already have jail.conf, which contains the defaults, then we have
jail.local with local defaults, then defaults-debian with even more
defaults (but actually only enabling ssh and not setting any other
defaults)... and if the user wants to really modify defaults, he'll
probably create a jail.d/default.conf, since these are his defaults and
not debian's...

Cheers,
Chris.