News for hackers. Stuff that matters.
Re:Practical Linux Hardening Guide by ynezz on Thursday January 24, 2019 @05:53PM (#18993885)
That's really terrible recommendation. You should add firewall rules and allow SSH access only from trusted hosts, ideally over VPN. It's not about login attempts but about possible bug in SSH (and other network services), because it's all just software, written in C, so believe it or not, but it's there, it's not if but when.
Re:Practical Linux Hardening Guide by wahern on Friday January 25, 2019 @12:56AM (#18995885)
The firewall isn't immune to exploitable bugs: https://nvd.nist.gov/vuln/detail/CVE-2017-18017

Likewise for VPN stacks: https://nvd.nist.gov/vuln/detail/CVE-2017-7521

If you're not prepared to expose a service to the world, you probably should run it at all. Ad hoc, non-standard configurations add substantial complexity and maintenance burdens. Complexity is the enemy of security, and having less time to manage more complex configurations is not a good recipe.

If you really need a service, then choose the best one and move on. The rule of thumb is that if you can reach a service, you should assume anybody else can, as well. This is especially true regarding SSH. I've seen plenty of servers p0wned via SSH, but never by breaking SSH. Instead the vector was always through an SSH user's computer infected by malware.

You want secure SSH? Disable password authentication and force everybody to use smartcard authentication like a Yubikey. I do rate limit SSH access using OpenBSD PF, but only because the authentication failures fill up and pollute the logs.

Re:Practical Linux Hardening Guide by vinay_ys on Friday January 25, 2019 @02:38AM (#18996233)
Have you seen yubikey/smartcard being used for sshin a large team? Would love to hear about your setup and learnings.
Re:Practical Linux Hardening Guide by xorcist on Friday January 25, 2019 @07:42AM (#18997423)
OpenSSH is solid piece of software. It hasn't had any (public) authentication bypasses that wasn't configuration related since it started to look like it looks today. Multiple skilled teams have looked at it thoroughly since. It has also been hardened with things like privsep and sandboxing.

This is not OpenSSL. Language alone does not make a product insecure. For practical purposes it is certainly not just a matter of when.

Contrast that with your VPN product, which probably falls over if someone looks at it funnily. Unless your product is called Wireguard, and we are ten years in the future, perhaps.

Re:Practical Linux Hardening Guide by leeoniya on Thursday January 24, 2019 @05:55PM (#18993897)
> That's really terrible recommendation

it would be if it was meant to be comprehensive.

Re:Practical Linux Hardening Guide by jesterson on Thursday January 24, 2019 @08:50PM (#18994855)
Absolutely this. Sad to see how many people refer changing ssh port to non-standard as "security" measure.
Re:Practical Linux Hardening Guide by icedchai on Thursday January 24, 2019 @05:56PM (#18993901)
Every little bit helps. I have hosts I access from "where ever."
Re:Practical Linux Hardening Guide by fencepost on Saturday January 26, 2019 @03:18PM (#19008204)
It's fallen out of favor these days, but if you're running on firewalls that can be configured for port knocking consider doing that. A non-sequential knock pattern that unlocks the remote IP for X amount of time can prevent a ton of grinding attacks.
Re:Practical Linux Hardening Guide by romeisendcoming on Monday January 28, 2019 @01:40PM (#19019884)
Add a TLS auth channel to the portknock with a wait window and OTP and you are really in business with this approach.