News for hackers. Stuff that matters.
Re:Brute.Fail Watch brute force attacks in real time by NavinF on Friday June 02, 2023 @07:38PM (#36172206)
Because it doesn't solve any real problems if you have ssh password login disabled and filter out login failures from logs
Re:Brute.Fail Watch brute force attacks in real time by bombela on Friday June 02, 2023 @08:24PM (#36172482)
With port knocking or a simple as having SSH on a non-standard port, the connection request stops before even opening the TCP connection. That's less load on the system, less logs, less writing to storage, etc. Less of what you don't want must surely be preferable.
Re:Brute.Fail Watch brute force attacks in real time by 9dev on Saturday June 03, 2023 @03:49AM (#36174592)
…all for the cost of vastly increased complexity. You’re just micromanaging your pets there. If the load of failed login attempts or the log writes brings your servers down, you have a whole lot of other problems to take care of.
Re:Brute.Fail Watch brute force attacks in real time by NavinF on Saturday June 03, 2023 @04:10AM (#36174688)
Are we talking about ssh on an ESP32 or a 2U server? You'd saturate my transit port before I noticed the load on my server or the logs that I filter by default.

btw TCP is cheap compared to public key crypto