News for hackers. Stuff that matters.
Re:Brute.Fail Watch brute force attacks in real time by bandrami on Friday June 02, 2023 @06:51PM (#36171860)
20 years ago port-knocking was supposed to solve this issue for good but it seems to have been never really been taken up. I'm not sure why.
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

Re:Brute.Fail Watch brute force attacks in real time by corn13read2 on Friday June 02, 2023 @08:15PM (#36172425)
This is really only effective for password based logins, but most logins these days are key based
Re:Brute.Fail Watch brute force attacks in real time by bandrami on Saturday June 03, 2023 @12:03AM (#36173592)
No, it cuts the DOS resource usage by a factor of 4 because a TCP connection is never opened.
Re:Brute.Fail Watch brute force attacks in real time by wkat4242 on Friday June 02, 2023 @08:49PM (#36172626)
Port knocking as it's usually done is easily sniffed. Perhaps using a dynamic TOTP-like time based seed to constantly rotate the ports might help. But it sounds overly complex.

It feels very like a "key under the third plant on the right" kinda thing. Not a solid security measure.

Re:Brute.Fail Watch brute force attacks in real time by matheusmoreira on Friday June 02, 2023 @11:38PM (#36173468)
Single packet authorization. It's like the server is not even there unless you send a cryptographically signed packet

https://cipherdyne.org/fwknop/docs/SPA.html

Re:Brute.Fail Watch brute force attacks in real time by wkat4242 on Saturday June 03, 2023 @08:24AM (#36176063)
Nice solution. I hadn't heard of it. I immediately thought of replay attacks because it's a one-way protocol but it looks like they mitigated those as well.
Re:Brute.Fail Watch brute force attacks in real time by 0cVlTeIATBs on Friday June 02, 2023 @11:38PM (#36173472)
Moxie Marlinspike made something to address the simple knock server's problems.

https://archive.is/MZKkb

Re:Brute.Fail Watch brute force attacks in real time by Gordonjcp on Saturday June 03, 2023 @05:17AM (#36175024)
This is fine, though. "Security through obscurity is not security" but moving your SSH port to something not 22 will utterly eliminate brute force attacks.

It's too much bother to go find it, and the bozos will just move on to the next machine with port 22 open.

Re:Brute.Fail Watch brute force attacks in real time by wkat4242 on Saturday June 03, 2023 @05:46AM (#36175162)
That's still not really security but just a nuisance mitigation IMO :)
Re:Brute.Fail Watch brute force attacks in real time by Gordonjcp on Saturday June 03, 2023 @05:51AM (#36175189)
It's both, really. If you're not getting scanned, you've reduced an attack surface, and that can only be good.
Re:Brute.Fail Watch brute force attacks in real time by wkat4242 on Saturday June 03, 2023 @08:19AM (#36176029)
Well, I view it as hiding an attack surface. It's still there, just harder to find.

But I know I'm a bit of an absolutist on security.

Re:Brute.Fail Watch brute force attacks in real time by Gordonjcp on Saturday June 03, 2023 @06:12PM (#36181020)
You put a lock on your bike.

But you also put it in the shed, and lock the shed.

Re:Brute.Fail Watch brute force attacks in real time by jlund-molfese on Saturday June 03, 2023 @09:23AM (#36176472)
Nuisance mitigations are part of security too! Fewer irrelevant notifications makes it more likely you’ll notice when something really is a problem.

It’s like how an adversary might launch a DDoS attack at the same time as they exploit a SQL injection vulnerability to exfiltrate credit card information. Filling up logs and alerts overwhelms the blue team and makes it harder to notice the quieter, but more dangerous attack.

Re:Brute.Fail Watch brute force attacks in real time by oh_sigh on Saturday June 03, 2023 @10:24AM (#36176941)
Security through obscurity actually is security, and is perfectly valid to use with a defense in depth strategy. The problem is when obscurity is the only defense.
Re:Brute.Fail Watch brute force attacks in real time by bigkm on Saturday June 03, 2023 @12:54PM (#36178244)
I agree, these attacks are looking for systems that have pretty default security, and by running on a different port you avoid all this automated chaos because you're non default now. Like scam emails with typos, a way to filter out the naïve people.