Re: SSH & VPN's (fwd)

["Adam Williams" <awilliam@xxxxxxxxxxxxx>]

On Dec 23,  5:51pm, root wrote:
> Subject: Re: SSH  & VPN's (fwd)
>
>
> From: mike <troll@net-link.net>
> To: Shawn Mattingly <smattin@net-link.net>
> Cc: Kazoo Linux Users Group <klug@deepthought.dyndns.com>
> Subject: Re: SSH  & VPN's
>
> If I'm snoopy as login, 1e2l3v4i5s as password and I'm trying to connect
> to linuxware.com, what would the command look like? Any suggestions?
> I've had several failed attempts to use this shell and I'm looking for a
> quick and dirty suggestion. And it's not my real login or password <:)
>

I assume you mean SSH.  I tried a long time ago to set it up by reading the man
page and failed miserably.  It was one of those instances of "JUST TELL ME HOW
TO DO IT!"  I did finally find a doc that did just that,  here is the low down.

Have the ssh deamon (sshd) running on the remote host
(were assuming they haven't used wrappers or something to disable your home net
from connecting).

Have ssh installed on your machine.

Run ssh-keygen to make a public and private key.  Your public key will be
stored in ~/.ssh/identity.pub and your private key in ~/.ssh/identity.  Never
ever give away or transmit your private key.

Append your public key (identity.pub) to the ~/.ssh/authorized_keys file on the
remote host,  from the home directory of the user you will be logging in as.
 If the file does not exsists just rename your identity.pub file to
authorized_keys.

Now you should be able to connect with a command like:

ssh -l <remote login account>  <remote host name>
  for an uncompressed connection

or

ssh -C -l <remote login account> <remote host name>
  for a compressed connection


That's all there was to it for me.

P.S. I'd also make sure that the file permission on the .ssh directory on the
local machine are tightened up,  as that holds your private key,  so only you
should be able to get at it.