|
|
|
|
|
|
|
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
One of the most popular ways to remotely administer a Linux system is using SSH. SSH provides an encrypted command line session from any remote machine. It's the secure replacement for the once ubiquitous telnet application. These days using telnet is frowned upon since it sends all data unencrypted in clear text. This step is totally optional, but if you want to work on your machine remotely, this is one of the best methods. First, install the ssh package:
Firewall:~# apt-get install ssh
The Debian package will prompt you for a few options. Select Yes to all three options: allow SSH version 2 only, run setuid, and install the server.
Our configuration file for this daemon is /etc/ssh/sshd_config
Firewall:~# nano -w /etc/ssh/sshd_config
Most of the defaults should be fine here. Personally I like to change PasswordAuthentication to yes, assuming you want to log in using your account password. Read through the configuration files, and change anything you want.
Depending on the firewall policy you set up earlier, you may or may not need to make adjustments. If you used the example policy of accepting all local traffic to anywhere, then SSH should be accessible from any local machine. You can also allow access from the internet by creating an instance in the /etc/shorewall/rules file, if you're feeling brave. Finally, if you want to tighten security, you can adjust the rules to only allow specific local machines to access the SSH port. This is great in an office network where only the administrator's workstation should have access.
|
|
|
|
|
|
Proceed to Step 10 - NTP |
|
|
|
|
|
|
|
|
|
|
| Copyright © 2006 Matt LaPlante. All rights reserved. |
|
Page created in 0.0021 seconds.
|
|
