3 ms·
There's this person you are thinking of who is actually vulnerable to something an SSH scanner is looking for. What I'd like to know is, what is that person rea
by jodrellblank 16y ago
There's this person you are thinking of who is actually vulnerable to something an SSH scanner is looking for. What I'd like to know is, what is that person reasonably going to do when his portscan detector goes off? Why didn't he do it a month ago instead of waiting?
Auto-ban the source of the portscanning, and limit what the now-known-hostile source IP can do next.
This person is probably doing nothing more than an automated nightly security update. Someone running an exploit against SSH which may work is bad, someone unable to run an exploit against SSH because they didn't find it before being blocked by an intrusion detection system is better.
And, because it wasn't scanning a month ago.
I hope my comments here are of the nature of "My mind is boggling as to why smart people think these measures are anything but laetrile." Also: do you think I'm just making it up? Don't be passive-aggressive. If you think I'm full of it on this topic, just say so.
They are of that "lol, dumbasses" nature. That's annoying and unhelpful. The submission is an article where the author explains some specific thoughts on some specific potential security measures, your replies are of the nature "lol no; ha ha nope; wrong again". I don't claim your view is wrong, but neither are you giving any of us mere mortals anything more to go on than trusting your reputation.
Great, "SHA-512 is plutonium", that's gonna help me what ... be afraid of it? "None of these security measures do anything to improve security"? Well that's literally not true, so are you merely claiming that they do to little to be worth it? Or what?
"People do things they think are heplful but which aren't helpful so we feel less powerless"? No, we do them because we think they help. That's just an ad-hom.
Changing the SSH port to a random one makes a scan to find it 32,000 times more effort, on average. The author claims that makes it too expensive for people to scan for. You claim it's "obvious" where you put it so it doesn't help. Well it isn't obvious where you put it. It just isn't. You do have to scan for it.
- tptacek 16y ago1. Your comments seems premised on the notion that OpenSSH vulnerabilities are routine. They are not routine. They are not hard to keep up with. And if you do not keep up with them, nothing you do is going to protect your server. I am reading tea leaves to arrive at this conclusion about your mindset, yes, but it's still worth pointing out. 2. Blocking sources is a silly way to defend against a server. Anyone who is actually using SSH exploits to break into servers has lots of sources. Meanwhile: anything a scanner is looking for, you're not vulnerable to; if you were, you're already owned. All blocking the source does is make you feel btter. 3. Yes, you should be afraid of using SHA-512. Yes, that is the point of that comment. 4. "32,000" sounds like a large number on a message board, but write an evented port scanner† and see how big that number really is. † Programming Challenge Level: 3 (Casual Comment On Hacker News - http://news.ycombinator.com/item?id=2317547)* http://news.ycombinator.com/item?id=2317547)*.