John Goerzen schrieb:
On Fri August 31 2007 8:13:25 am Patrick Matthäi wrote:
Oh I'm sorry, I didn't meant the unix console, I meant the bacula console
:)
I really believe that upstream will see this as a feature. I'm not going to
patch this locally in Debian. If you like, I could forward it to them, but
I suspect they will say that you should be using hosts.deny to filter out
misbehaving IPs anyway.
What do you think?
-- John
The clue is, that our monitoring system checks, if the -sd -fd and
-director is available outside from the server, with simple tcp socket
checks (port open or not?). The monitoring checks it every second
minute, so there are always a lot of errors inside of the bacula log /
console and in the emails (okay that one with the emails have I solved ;)).
The sshd won't tell you, too, if anyone checks if port 22 is open, this
would be annoying, so I think this isn't very right.
I think the right thing would be, if I get a notice, if another process
tried to authenticate really, not how our monitoring system, which just
checks if there's something behind this port.
Regards,
Patrick Matthäi
