Live data from Hacker News

What you should do in your first 5 mins of a new server install

engineering.timbrook.im

1–6 of 6 posts

Re: What you should do in your first 5 mins of a new server install

#3
post #2

I'm a big proponent of changing the SSH port. That right there makes life a lot easier when dealing with brute force attempts. You can also make an IP tables taste limit on that port.

My only excuse for not changing port is workflow, needing to add the flag or : on the address is too much :P

Re: What you should do in your first 5 mins of a new server install

#4
post #3
post #2

I'm a big proponent of changing the SSH port. That right there makes life a lot easier when dealing with brute force attempts. You can also make an IP tables taste limit on that port.

My only excuse for not changing port is workflow, needing to add the flag or : on the address is too much :P

that's what the .ssh/config file is for

Re: What you should do in your first 5 mins of a new server install

#5
post #3
post #2

I'm a big proponent of changing the SSH port. That right there makes life a lot easier when dealing with brute force attempts. You can also make an IP tables taste limit on that port.

My only excuse for not changing port is workflow, needing to add the flag or : on the address is too much :P

You can define globals on your machine.

ssh $main or ssh $mail

Makes it even easier, don't need to remember domain, port, or user.

Re: What you should do in your first 5 mins of a new server install

#6
post #4
post #3

Earlier quoted context omitted.

My only excuse for not changing port is workflow, needing to add the flag or : on the address is too much :P

that's what the .ssh/config file is for

Wow, I never knew that was possible from the SSH config [0]. Thanks for the pointer! Time to update all of my settings!

[0] - http://www.cyberciti.biz/faq/create-ssh-config-file-on-linux...