Are you by any chance the Mike Harris who was serving in Japan and
went under the nick of Lotus?  If so, greetings from OldMonk.  If not, 
please ignore this message and sorry for the inconvenience.

Regards,

>>>>> "Mike" == Mike A Harris <[EMAIL PROTECTED]> writes:

    Mike> On Wed, 2 Jun 1999, Hugo Bouckaert wrote:
    >> Suppose I want to connect using ssh from machine A to B. Do I
    >> have to set up ssh on both machines? What precisely? - is there
    >> a host client relationship. If I want to use ssh over a
    >> network, do I set up ssh on all machines? Which ones are host
    >> and which ones clients?

    Mike> ssh, like any other major TCP/IP service is composed of a
    Mike> server application (sshd) and a client application (ssh).
    Mike> This client-server model works identical to any other
    Mike> client-server protocol out there including telnet.

    Mike> To connect to a remote machine from a local machine using
    Mike> ANY protocol, you run the client on the local machine, and
    Mike> the server on the remote machine.  ssh is no different.

    Mike> ssh needs to be installed on all the machines, otherwise how
    Mike> can one connect to a machine that doesn't have a daemon
    Mike> monitoring incoming connections?

    >> Once ssh is set up, as an ordinary user, what do I do to set up
    >> the keys.

    Mike> ssh-keygen

    >> How do the keys work. Where is the so-called public key and
    >> priovate key kept. How does that work.

    Mike> They are kept in .ssh/identity, and .ssh/identity.pub as
    Mike> explained on the ssh-keygen, and I believe also the ssh
    Mike> manpage.

    Mike> The workings of it are discussed on the ssh manpage as well,
    Mike> but are not very clear from an end user perspective IMHO.
    Mike> I'm still fighting to fully understand it.

    Mike> Good luck, TTYL

    Mike> -- Mike A. Harris Linux advocate GNU advocate Computer
    Mike> Consultant Open Source advocate

    Mike> Tea, Earl Grey, Hot...

Reply via email to