Hacker Read top | best | new | newcomments | leaders | about | bookmarklet login

But what does deter them is port knocking. We went from many attempts per hour to not a single one since adding port knocking to our firewall.

Port knocking has been mentioned before on HN and it generally gets a luke warm to negative response. It completely baffles me, this response.



view as:

It's just caution. Using port knocking by itself would be a recipe for security disaster. As an addition to an already secure system, it's okay if you just want to reduce junk in your logs, perhaps. Many would ask, in that case, why use port knocking at all?

The is the usual thing I hear. It is so incredible naive, though.

Any service, no matter how locked down and properly configured, still presents an attack surface. SSHD is a program like any other, and it can have bugs.

When you use port knocking with a properly configured SSHD, you are much more secure because that attack surface has been removed.


Seems like quite a bit of work to avoid a few connections an hour. Are you paying $0.01 per byte for syslog entries or something?

Who cares about a few connections per hour if the sun will die before they brute force your private key?


Legal | privacy