-This document is very detailed so that a new user can be familiar with the environment.

-

-If you try to ssh to a newly installed dfly from another system you will get this error

-

-

- $ ssh root@172.16.50.62

- ssh: connect to host 172.16.50.62 port 22: Connection refused

-

-This is because sshd is not up and running on dfly.

-At this point if you check /etc/ssh you will only have the following files

-

-

- # ls /etc/ssh

- blacklist.DSA-1024 blacklist.RSA-2048 ssh_config

- blacklist.DSA-2048 blacklist.RSA-4096 sshd_config

- blacklist.RSA-1024 moduli

-

-You don't have any SSH host keys generated for the system yet!

-

-When you start sshd for the first time it is best to start it through the <b>"/etc/rc.d/sshd"</b> script which will automatically generate the host keys. For this to work right you need to do the following steps (these steps are not essential for DragonFly 2.8.2 since sshd is already enabled in rc.conf)

-

-1) Enable sshd in rc.conf

-

- #echo "sshd_enable=yes" >> /etc/rc.conf

-

-2) Start the sshd server using the rc script

-

-

- # /etc/rc.d/sshd start

- Generating public/private rsa1 key pair.

- Your identification has been saved in /etc/ssh/ssh_host_key.

- Your public key has been saved in /etc/ssh/ssh_host_key.pub.

- The key fingerprint is:

- ........

- Generating public/private dsa key pair.

- Your identification has been saved in /etc/ssh/ssh_host_dsa_key.

- Your public key has been saved in /etc/ssh/ssh_host_dsa_key.pub.

- The key fingerprint is:

- ........

- Starting sshd.

-

-Now if you go back and look in /etc/ssh you will find the SSH host key files too.

-

-

- # ls /etc/ssh

- blacklist.DSA-1024 moduli ssh_host_key.pub

- blacklist.DSA-2048 ssh_config ssh_host_rsa_key

- blacklist.RSA-1024 ssh_host_dsa_key ssh_host_rsa_key.pub

- blacklist.RSA-2048 ssh_host_dsa_key.pub sshd_config

- blacklist.RSA-4096 ssh_host_key

-

-

-At this point if you try to ssh to the dfly you will get the following error

-

-

- $ ssh sgeorge@172.16.50.62

- The authenticity of host '172.16.50.62 (172.16.50.62)' can't be established.

-** It is not advisable to allow Root Login with password especially if your System is connected to the Internet unless you use Very Strong Passwords. You could be a victim of [ssh password based brute force attacks](http://en.wikipedia.org/wiki/Password_cracking#Brute_force_attack). If you are victim of one such attack you can find entries like the following in your** ****"/var/log/auth.log file"****.