3 ms·
I and I suspect many like me realise that the truth lies somewhere in the middle. Do I use security-by-obscurity? Of course! I know that my server is going to
by Gordonjcp 4y ago
I and I suspect many like me realise that the truth lies somewhere in the middle.
Do I use security-by-obscurity? Of course! I know that my server is going to get hammered with attempts to steal info, and I can see /path/to/webroot/.git/config getting requested several times an hour, so I don't put important stuff in places where it might be accessed. Even giving it a silly name won't help, it has to be simply not something that's there at all. That kind of security-by-obscurity is asking for trouble.
Sure as hell though, if I move ssh off of port 22 then the number of folk trying to guess passwords drops to *zero*, instantly.
- creeble 4y ago>Sure as hell though, if I move ssh off of port 22 then the number of folk trying to guess passwords drops to zero, instantly. But not for very long. But it doesn't matter, but for log annoyances.
- bombcar 4y agoI’ve found dictionary attacks against non-22 ssh to be effectively zero. Maybe once in awhile you get a port scan and a poke or two, but anyone able to move ssh off of 22 is not likely to have the password “p4ssw0rd”
- Gordonjcp 4y agoIt's a bit like the bit with the fake tan in Neuromancer. "You think that looks real?" "Nah, but it looks like you care enough to fake it." If you care enough to move your ssh port you're probably not totally clueless at best, and at worst you're setting out bait.