[We need to finally settle on a logo]
... although we have done fine without one for years and years

And test that it works

Once one or both of the keys are transferred into the virtual instance, it is time to switch back to the terminal, and do some testing. From the .ssh directory, we use the following commands:

ssh -i pmman-id_dsa -l root
# we had previously (in testing) accepted the remote host's ssh host key
# 'fingerprint' as trustworthy, which is a way to detect a 'man in the
# middle' compromise
# then we are locally prompted for the 'passphrase' of the local pmman-id-rsa
# private key with that key unlocked for use, SSH generates a series of
# transfers in stages that prevent exposure of that unlocked key to a
# potential eavesdropper, and the session on the remote host is opened
# through an encrypted communications channel

The terminal prompt changes to [root@vm049244170 ~] signalling that one is on another host, and in the user level of the root user. This was set with the -l root option in the initiating ssh command. We move into the .ssh subdirectory, and examine the public key, as held in the authorixed_keys file. As may be seen, this matches the value of the public key we dumped out back on the initiating OS/X host

cd .ssh
cat authorized_keys | grep ssh-dss

At this point, we have established the ability to do normal systems administration through that ssh connection. A good first step would be to set up an end user account, and ssh2 keyed access for it.


[  Top  |  About  |  Pricing  |  Sign Up  |  LOG ON  |  Tour  |  News  |  Support  |  Media  |  Site Map  |  EULA  |  Legal  |  DMCA  |  Contact  ]

Copyright © 2009 .. 2013 PMMan.com, a division of 781 Resolution, LLC