HP NonStop SSH 544701-014 Reference Manual page 45

To Export the Public Key and Configure it on the Remote System
The following command within SSHCOM will export the public part of the key just generated and write it into a file:
$DATA1 SSH2 7> run sshcom $ssh01
T9000B03_02DEC2009_SSHCOM
OPEN $ssh01
% export key comf.tb:test1, file $data1.tbtmp.tbkey, format openssh
export key comf.tb:test1, file $data1.tbtmp.tbkey, format openssh
OK, key comf.tb:test1 exported
%
Note: If you are executing SSHCOM as SUPER.SUPER, you will need to switch to CLIENT mode before exporting the
key. Please issue following command before the EXPORT KEY command:
MODE CLIENT
The file $data1.tbtmp.tbkey now needs to be transferred to the remote system in BINARY mode. Note that the file
contains only the public key and therefore contains no sensitive information.
The public key exported to the tbkey file can now be transferred to the remote system. The next step will configure the
public key for the remote user.
To Configure the Public Key on the Remote System
The OpenSSH implementation keeps a directory called ".ssh" for each user. A file named "authorized keys" is located in
the .ssh directory that contains the public key of each trusted key of a remote system. In order to add the public key
contained in the file created in the prior step, the UNIX command "cat" can be used to add the content to the existing
content in the file. The following commands are again executed on the remote system, this time using "normal user"
logon credentials.
burgt@np-dev:~> pwd
/home/burgt
burgt@np-dev:~> cd .ssh
burgt@np-dev:~/.ssh> more pubkey
ssh-rsa
AAAAB3NzaC1yc2EAAAABEQAAAIEAkdR/ncHRVEJteOC1EMSkMgrrXpdcc6Lkejp7mcFKYNa0tMqP4eknTyFXUX
2jm1K7AKDh1Je52aqNJTBAIPIM
Bt+HboBKwjuZtb2+f1HG4LEA71NymoVcuABVyr1DvWPtpNzCNjaD0qdkR9yMlDZH/DCD/OqdneLJQ8B3RXbKl1
U= TB's RSA key
burgt@np-dev:~/.ssh> cat pubkey >> authorized_keys
burgt@np-dev:~/.ssh>
In the commands above
•
The user's home directory is /home/burgt .
•
The public key was transferred to the remote system under the location /home/burgt/.ssh/pubkey .
•
The final command adds pubkey to authorized_keys. Please note the double '>>'; if you use only one '>', you
will overwrite authorized_keys with the content of pubkey.
After this step you can now retry the step "To connect with a remote SSH client". You will not be prompted for the
remote user's password. Instead, SSH2 will use the key pair configured for your NonStop user ID.
HP NonStop SSH Reference Manual
Installation & Quick Start • 45