| 1 |
On Sunday 16 October 2005 09:18 pm, Nick Rout wrote: |
| 2 |
> no, you just type: |
| 3 |
> |
| 4 |
> ssh my.network.com |
| 5 |
> |
| 6 |
> Depending on your setup you will probably need to set your |
| 7 |
> firewall/router to forward port 22 to the machine you want to log into. |
| 8 |
> Also make sure your ssh server is set up securely. |
| 9 |
|
| 10 |
This last statement really needs to be highlighted for all of the newbies out |
| 11 |
there... |
| 12 |
|
| 13 |
Just opening port 22 will expose your system to attempted break-ins. If you |
| 14 |
look at your authorize.log (or relevant log depending upon your syslog |
| 15 |
config), you'll see after a couple of days different systems accessing ssh an |
| 16 |
trying to log in as root and/or other users. |
| 17 |
|
| 18 |
Unless you really feel comfortable with your own security infrastructure, your |
| 19 |
best bet is to edit your /etc/ssh/sshd_config file and change the port number |
| 20 |
to only something you'd think of in the higher range of port numbers. |
| 21 |
|
| 22 |
It will still be open, you'll still be able to hit the box from anywhere |
| 23 |
outside your network, but the different port number ensures that random port |
| 24 |
scans and breakin attempts will be significantly lower than if you just tried |
| 25 |
to use standard port #22. |
| 26 |
-- |
| 27 |
gentoo-user@g.o mailing list |
Archives