Re:Cache on Delivery (Mining random people's memcached)
by KTamas on Thursday August 05, 2010 @04:54PM
(#1579316)
Oh yes, the first thing I do is change the SSH port, eleminates 99,99% of the auth attacks.
Re:Cache on Delivery (Mining random people's memcached)
by Vivtek on Thursday August 05, 2010 @06:08PM
(#1579507)
Damn. Why didn't I ever think of that? I'm doing that tomorrow.
Re:Cache on Delivery (Mining random people's memcached)
by dugmartin on Thursday August 05, 2010 @09:20PM
(#1579889)
Remove root login over ssh and disable password logins and you are good to go. If you want to get fancy Google for ssh port knocking.
Re:Cache on Delivery (Mining random people's memcached)
by mrduncan on Friday August 06, 2010 @11:18AM
(#1581242)
disable password logins
I can't emphasize this one enough. Unless you need to login from a lot of different machines, there really isn't any excuse not to do this. It also has the bonus of making logins really easy since you don't have to type a password.
Re:Cache on Delivery (Mining random people's memcached)
by InclinedPlane on Saturday August 07, 2010 @06:56PM
(#1584520)
If you host your systems on a VPS service like linode or slicehost then you have the backup of a web based console in case you screw up royally and have a HD crash on the one machine your SSH key was on (for example).
Re:Cache on Delivery (Mining random people's memcached)
by KTamas on Sunday August 08, 2010 @06:58AM
(#1585181)
Heh, port knocking looks cool, might do that just for the heck of it on a server that only I use.
Also, yes, among with changing the port the only way that should be possible to get in is through 'keys.
That alone allows you to avoid most attackers trying to guess valid server ips.
Now to put a honey pot on port 22.