Package: dovecot-core
Version: 1:2.1.7-7
Followup-For: Bug #696926
Dear Maintainer,
*** Please consider answering these questions, where appropriate ***
* What led up to the situation?
using fail2ban is impossible without tcpwrapper support if run in chroot or
environement where iptable cannot be used. TCPwrapper is a basic security
mecanism that was here on squeeze and seems to be also on sid so why not in
stable ?
this is really a plus to be able to stop brute fore password guessing
aptempts
* What exactly did you do (or not do) that was effective (or
ineffective)?
tested access in several config scenario, even with the fact that dovecot is
uploaded with a 10-tcpwrapper.conf config file the tcpwrapper support seems
missing in the binary . I tested it and got errors at server launch.
* What was the outcome of this action?
dovecot ignores completly hosts.deny/allow file
* What outcome did you expect instead?
that dovecot honors it as it do in squeeze/lenny and it seems in sid.
*** End of the template - remove these lines ***
-- Package-specific info:
-- System Information:
Debian Release: 7.0
APT prefers stable
APT policy: (500, 'stable')
Architecture: amd64 (x86_64)
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
