Boston Linux & Unix (BLU) Home | Calendar | Mail Lists | List Archives | Desktop SIG | Hardware Hacking SIG
Wiki | Flickr | PicasaWeb | Video | Maps & Directions | Installfests | Keysignings
Linux Cafe | Meeting Notes | Blog | Linux Links | Bling | About BLU

BLU Discuss list archive


[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

ssh config question...



The simplest way is with a .shosts file.

Suppose I want a.b.com to trust connections from c.d.com:

1) On a.b.com, put "c.d.com <username>" in ~/.shosts  (which must be
read/writable only by owner (you)).

2) Now you have to let a.b.com really know who c.d.com is... use ssh
to make a connection from a.b.com to c.d.com.  Use the fully qualified
hostname, just as you entered in ~/.shosts.  If you haven't done that
before, it will ask if you really want to connect, since c.d.com is
not in ~/.ssh/known_hosts.  Say yes, that's the key.  You should be
able to ssh back to a.b.com without a password.

ssh-agent based authentication is nicer, but a bit more involved to
set up.

  jj

PS If you want to distribute files over an encrypted link, use "rsync" 
it efficiently does just that (by sending diffs if possible) and can
use ssh for transport.





BLU is a member of BostonUserGroups
BLU is a member of BostonUserGroups
We also thank MIT for the use of their facilities.

Valid HTML 4.01! Valid CSS!



Boston Linux & Unix / webmaster@blu.org