What you should do in your first 5 mins of a new server install
engineering.timbrook.im
What you should do in your first 5 mins of a new server install
1–6 of 6 posts
Re: What you should do in your first 5 mins of a new server install
#2You can also make an IP tables taste limit on that port.
Re: What you should do in your first 5 mins of a new server install
#3I'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.
Re: What you should do in your first 5 mins of a new server install
#4I'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
#5I'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
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
#6Earlier 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
[0] - http://www.cyberciti.biz/faq/create-ssh-config-file-on-linux...