On: Brute.Fail: Watch brute force attacks fail in real...

[operator-name]

I'd be cautious about stuff like this - if you annoy the wrong person that could paint a target on your back.

[dylan604 → operator-name]

Don't discourage someone else from doing it and risk their not coming back to update us on the results. This popcorn is not going to eat itself.

[Zetice → operator-name]

They're impotent little weasels who couldn't hit a target the size of a barn, so the risk is minimal.

[fsckboy → Zetice]

"do not guess that it will be your weakest opponent nor guess what they will try, prepare for your strongest adversary and all that they can do" -- mutatis mutandis, Sun Tzu, Art of War

[l33t233372 → fsckboy]

Not to disagree with infallible thousands of years old advice, but surely resources are in far shorter supply than potential attacks, so we have to prioritize and filter.

[capableweb → operator-name]

Realistically though, they'll probably timeout by themselves automatically if they haven't seen a password prompt after N seconds. TCP connections can hang overall, so having that would be basics anyway.

[myself248 → operator-name]

If this was default on port 22 of every cheap router sold, and if you enable ssh it has to go on some other port, it'd frustrate a lot of bad guys.

[internetter → operator-name]

Ah where's your sense of fun ;)