Hi,
we have recently been hit by a couple of brute force password attacks
against dovecot. So what I want to do now is to add dovecot to fail2ban
in order to block further attacks.
However, I don't seem to be able to find out password verifification
failures for our LDAP based user data.
T
Udo Rader schrieb:
Hi,
we have recently been hit by a couple of brute force password attacks
against dovecot. So what I want to do now is to add dovecot to fail2ban
in order to block further attacks.
However, I don't seem to be able to find out password verifification
failures for our LDAP
Udo Rader wrote:
Udo Rader schrieb:
Hi,
we have recently been hit by a couple of brute force password attacks
against dovecot. So what I want to do now is to add dovecot to
fail2ban in order to block further attacks.
However, I don't seem to be able to find out password verifification
fail
Udo Rader schrieb:
Udo Rader schrieb:
Hi,
we have recently been hit by a couple of brute force password attacks
against dovecot. So what I want to do now is to add dovecot to
fail2ban in order to block further attacks.
However, I don't seem to be able to find out password verifification
fa
Seth Mattinen schrieb:
Udo Rader wrote:
Udo Rader schrieb:
Hi,
we have recently been hit by a couple of brute force password attacks
against dovecot. So what I want to do now is to add dovecot to
fail2ban in order to block further attacks.
However, I don't seem to be able to find out passw
Udo Rader wrote:
Seth Mattinen schrieb:
Udo Rader wrote:
Udo Rader schrieb:
Hi,
we have recently been hit by a couple of brute force password
attacks against dovecot. So what I want to do now is to add dovecot
to fail2ban in order to block further attacks.
However, I don't seem to be able
Seth Mattinen schrieb:
Solved it myself, adding changing to "auth_verbose = yes" in
dovecot.conf solved it.
Any reasons why this isn't enabled by default?
Because it's a debugging switch.
hmm, that's weird then.
Without turning on this "debugging switch" (LDAP) authentication
failures ar
