News for hackers. Stuff that matters.
Re:Cache on Delivery (Mining random people's memcached) by maukdaddy on Thursday August 05, 2010 @09:46PM (#1579944)
Restrictions on port 22 are NEVER overkill. In fact, you should run another port entirely.
Re:Cache on Delivery (Mining random people's memcached) by _delirium on Thursday August 05, 2010 @09:51PM (#1579956)
If you're already using key authentication, that doesn't add much security. A port is just a very short password shared by all users--- instead of logging in with "I'd like to login, please initiate public-key authentication", you now have to login with "I'd like to login, the magic number is 2222, and please initiate public-key authentication", which isn't really any more secure.
Re:Cache on Delivery (Mining random people's memcached) by peripitea on Thursday August 05, 2010 @11:27PM (#1580095)
Call me an engineer, but I don't understand why anyone would dismiss security through obscurity just because it's theoretically useless. If you can reduce the lifetime expected value of successful attacks on your system, it should be considered a win regardless of how you do it. (Of course, relying solely on security through obscurity is a sure-fire way to greatly increase said EV.)
Re:Cache on Delivery (Mining random people's memcached) by billpg on Friday August 06, 2010 @04:17AM (#1580522)
It will deflect a lot of network-capacity-wasting opportunistic attempts if the masses don't even realise there's an SSH port there.