Software informational articles

In a row a curriculum on a aloof ma?tre d'h?tel using ssh - software


How do you run a course on a cool attendant using ssh?

For this exemplar we'll have two servers, one named Johnny and a further named Cash. Both are in a row openssh. Our goal is to have a course on Johnny login to Cash and run a curriculum on Cash. To make the task a hardly more composite we'll be using another users on each machine.

The first thing we'll need to do is engender civic and clandestine keys on Johnny. So, logged into Johnny as user 'boy' we construct communal and concealed keys by creating them in the . ssh almanac as follows:

Johnny$> pwd

/home/boy/. ssh

Johnny$> ssh-keygen -t rsa -f sue

Generating public/private rsa key pair.

Enter passphrase (empty for no passphrase):

Enter same passphrase again:

Your identification has been saved in sue.

Your civic key has been saved in sue. pub.

The key fingerprint is:

8d:e9:c0:g1:c7:1f:e3:b3:2f:38:12:aa:b5:3b:2e:b3 boy@Johnny


In the case above we singled out an random name, sue, to associate the files that hold the generated keys. When prompted to enter a passphrase (twice) we cleanly hit enter twice.

As the amount produced of ssh-keygen indicates, the broadcast key has been saved in a file named sue. pub.

The amount produced of ssh-keygen implies, but doesn't denote directly, that the clandestine key is in a file named sue (Yes, a user named boy produced a file named sue. )

Johnny$>ls -l

-rwx------ 1 sue suegrp 887 Oct 17 14:27 sue

-rwx------ 1 sue suegrp 223 Oct 17 14:27 sue. pub

The clandestine key file, sue, will hang about on Johnny for the reaminder of this exercise, but the community key must be moved to the apart server, Cash. Note that the . ssh encyclopedia itself, as well as the sue and sue. pub files ought to have permissions of 700.

Now you'll need to ftp the sue. pub file from Johnny to Cash. The user on Cash that we'll login as is user 'named'.

Johnny$> ftp Cash

Connected to Cash

220 Cash - Propery of Xyz. - Certified users only

Name (Cash:boy): named

331 Password mandatory for named.


230-Last unsuccessful login: Fri Oct 17 13:12:55 2003 on ftp from Johnny 230-Last login: Fri Oct 17 16:02:11 2003 on /dev/pts/1 from Johnny

230 User named logged in.

ftp> cd . ssh

ftp> mput sue. pub

mput sue. pub? y

200 PORT appreciation successful.

150 Cavity data correlation for sue. pub.

226 Convey complete.

224 bytes sent in 0. 000781 seconds (280. 1 Kbytes/s)

local: sue. pub remote: sue. pub


221 Goodbye.


Now we'll telnet into Cash and concatenate the sue. pub file into /home/named/. ssh/authorized_keys file.

Cash$> pwd

/home/named/. ssh

Cash$> cat sue. pub >> authorized_keys

Cash$> exit

Connection closed.


Let's recap what we've done so far.

1) We've formed civic and confidential keys on Johnny.

2) We've ftp'd the community key file, sue. pub, from Johnny to Cash.

3) We've telnetted to Cash, and concatenated the inside of sue. pub into authorized_keys

We're now ready to manually login from Johnny to Cash using ssh.

Johnny$> ssh -i /home/boy/. ssh/sue named@Cash

The faithfulness of host 'Cash (xxx. yyy. zzz. aaa)' can't be established.

RSA key fingerprint is 65:11:7d:ef:ed:a3:cc:34:d1:b5:ba:c9:16:22:31:23.

Are you sure you want to go on linking (yes/no)? yes


*** Become aware of TO ALL USERS ***



Connection to Cash closed.


Now on Johnny, build a shell draft called 'boynamedsue. sh' with the subsequent one line of filling and chmod the handwriting to 777.

ssh -i /home/boy/. ssh/sue named@Cash /usr/bin/ls -l

Next, complete the lettering on Johnny.

Johnny$> boynamedsue. sh


*** Announcement TO ALL USERS ***


-rwxrwxr-x 1 named namedgrp 10020 Oct 17 14:35 namedfile1. txt

-rw-r--r-- 1 named namedgrp 680 Aug 14 16:18 namedfile. html

-rw------- 1 named namedgrp 1148 Aug 18 09:51 mbox

drwxr-xr-x 2 named namedgrp 512 Jun 17 13:38 old


You just executed a agenda on Johnny, that logged into Cash and ran a course (unix 'ls -l').

The next step you'll want to take is to put back the '/usr/bin/ls -l' be in charge in the boynamedsue. sh course with the path and name of the code that you want to run.

About The Author

C. S. Deam is a small affair owner. His eBook CPU Nuggets: Non-Techie Internet Tips For In-Laws, Out-Laws, and the Rest of Circle is a great gift for non-techie children members and is obtainable at www. LinkertonPublishing. com where you can sign up for FREE E-Courses & Newsletters to help you on your path to self-employment.

Developed by:
home | site map © 2018