3 ms·
Whatever happened to that port knocking idea a few years ago, did that go anywhere?
by jbooth 16y ago
Whatever happened to that port knocking idea a few years ago, did that go anywhere?
- draebek 16y agoLots of people seem to recommend port knocking still today, but I personally won't use it as I'd hate to get behind a firewall (e.g. hotel, airport, university) where I can't send the right sequence of knocks for whatever reason (outbound ports firewalled).
- uxp 16y agoI set it up a few months ago and ended up disabling it after a few weeks due to this reason. All my SSH servers have password authentication disabled and a strict AllowUsers list, anyways. The only thing I do externally from sshd is have a cronscript run every 15 seconds to grep my authlog file to find any IP addresses that fail authentication and put them in a global blacklist for my PF firewall. It cuts down the ssh authlog noise considerably, and rarely accidentally blacklists myself.
- Periodic 16y agoI had my internal monitoring system on a network I managed set up with port knocking. It ended up being more hassle than I thought it was worth, as it wasn't a box that was getting attacked much anyway. It's really pretty easy to set up with iptables in Linux. http://www.debian-administration.org/articles/268 http://www.debian-administration.org/articles/268