> Any ideas about what caused blocklistd to decide that my rather normal
> [ssh] activity was not good?
This is what had happend to me:
Sshd registers any attempted but non-matching ssh-key presented by
the with blocklistd and these can add up and eventuelly trip the
critical threshold. An eventually successful login doesn't reset
the bad marks collected by the prior failed attempts. (You can
see failed attempts with "ssh -v".)
The problem is more likely to show up with a client which accumulates
both older and newer key types or more keys in a key-agent.
The only solution is to use your .ssh/config and an "IdentityFile"
directive to present to proper key to the server from the get-go.
Martin Neitzel
