Re: SSH again!

["Timothy C. Phan" <tphan@iqrinc.com>]

Hi all,

  Thanks for all the replies.  I believed that I got it to
  work somehow.  Need to redo the steps again to make sure.

  Still, do not quite understand how all this work:

    1.  Can one steal/copy the *.pub keys and use it to logon?
    2.  It seemed to me that if I do not remember/supply the
        correct passphrase when run ssh, it would still 
        allow me to log on using the regular account/password.
    3.  Even if I do not have the *.pub keys and I could still
        log on the server via the regular login/password!

  I thought that if not public key were given to the client,
  the client shall not be able to log on regardless whether
  the client has or does not have the regular login/password.
  Otherwise, what is the point of having the key or not having
  the key?

  Last, how do I generate the key from a windows/nt machine?
  I'm trying to login from an windows / nt as well.  Thanks!


Bob Nielsen wrote:
> 
> On Thu, Jun 15, 2000 at 08:41:01AM -0500, Nathan E Norman wrote:
> > On Wed, Jun 14, 2000 at 04:23:38PM -0700, Bob Nielsen wrote:
> 
> > > Most of the systems on which I have set up a .ssh/authorized_keys file
> > > require only the key.  One requires the password instead, although the
> > > key file is correct as far as I can tell.
> >
> > It's worth noting that ssh cares about file permissions; it seems to
> > get upset if your key files are group writable.  Remove group write
> > permissions and see what happens.
> 
> The permissions for .ssh/authorized_keys on both boxes (both running
> slink) are: -rw-r--r--
> 
> The two files are identical, as well.
> 
> --
> Bob Nielsen, N7XY  (RN2)                   nielsen@oz.net
> Bainbridge Island, WA                      http://www.oz.net/~nielsen
> 
> 
> --
> Unsubscribe?  mail -s unsubscribe debian-user-request@lists.debian.org < /dev/null