3 ms·
> However, please consider adding our scanner (71.6.151.167) to your "whitelist". We are well-known cyber-sec researchers, we aren't trying anything nefarious o
by noir_lord 13y ago
> However, please consider adding our scanner (71.6.151.167) to your "whitelist". We are well-known cyber-sec researchers, we aren't trying anything nefarious or evil, and we are being as transparent as possible about our scans.
Sure and while we are at it I'll fetch the lube.
I don't complain about port 22 connections because none of my machines run anything on port 22 (I move SSH to a random port mostly to deter whatever is coming out of China this week).
Even if you do find the port you still have to get around the ssh key's (so unless you are the NSA (j/k)), you could try an exploit against ssh but as it doesn't report its version good look with that and do try to avoid triggering fail2ban.
I'm not a systems administrator (I guess I'd be DevOps) but I know enough to know I don't know enough to disregard best practice.
- laumars 13y agoI kind of like running SSH on the default port as it gives me a list of IPs to firewall against on other web facing services across my infrastructure. If someone is trying to break into my server(s) via SSH, then I sure as hell don't want them to have access to any other services regardless of how secure they might be.
- tlrobinson 13y agoCouldn't you just have your firewall log attempted connections to 22, regardless of whether or not you have SSH running on it?
- noir_lord 13y agoI've also seen people run a fake SSH server on 22 and log attempts (if you know that you don't use 22 then any connection attempt on 22 is interesting).
- laumars 13y ago"Just"? That requires more work to set up than my method and offers no additional security benefits as you're still running an open SSH port. You're falling into the common trap of security through obscurity. But in fact it's very easy to find which port SSH listening on even when you're using a non-standard on. However if you harden SSH properly then it doesnt matter what port it's listening on. So your method is more work for zero gain
- LukeShu 13y agoWhat? They aren't doing anything funny, nor are they asking you for permission to do anything funny. They scan your ports. To the unobservant, that can look like they are trying to crack your systems. What is wrong with recognizing their IP (adding it to your "whitelist"), and knowing that it probably isn't something worth investigating.
- stephengillie 13y agoAt the very least, you know their IP, so you can search your logs for it to make sure they aren't being evil.
- noir_lord 13y agoCall me a cynic (I don't mind) but they do the sweep of the whitelisted address and then two weeks later I get an attempted break-in from a completely different address.... I'm not white-listing anyone I don't know.
- kalleboo 13y agoYou won't whitelist someone because they'll try to break in from an IP other than the one you whitelisted? How does that even begin to make sense?
- pekk 13y agoI think you missed that he was responding to this: > so you can search your logs for it to make sure they aren't being evil. This argument doesn't apply if the probe and the attack come from different IPs
- njharman 13y agoWho exactly are "they"? Other than someone with a blog post saying whitelist this ip and claiming "no monkey business, promise!" No time/interest to vet them. Also, did their webpage get hacked and that ip changed? Will someone with access to their machines network succumb to maliciously using or selling access to this widely whitelisted ip? Seven years from now will that ip still be theirs?