Re: Plain & Simple . . .
From: Mike (mike_at_nomail.com)
Date: 11/27/03
- Next message: Vahid: "Re: problem after patching openssh 3.7.1p2"
- Previous message: Gregor Hoffleit: "Re: Using DynDNS names in authorized_keys"
- In reply to: marco_at_marcosoftware.com: "Plain & Simple . . ."
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Date: Thu, 27 Nov 2003 21:52:59 +0800
marco@marcosoftware.com wrote:
> We would like to use ssh2, and NOT enter a password.
>
> I have tried to read the documentation on this and haven't seen it anywhere
> in a plain and simple manner...
>
> 1) Create a hostkey.
> 2) Put it .ssh2/authorization?
> 3) Put it in .ssh2/authorized_keys?
>
> Someone please explain it simply!
>
>
> Thanks!
> M.
>
>
Making the assumption that you are using a default OpenSSH installation
at both ends on a unix system (these details would sure help)
1. Create a key pair (not a host key)
2. Copy the public part to ~/.ssh/authorized_keys on the remote machine
3. Copy the private part to ~/.ssh/id_rsa on the local machine
These file names are specified in the config files, so you may want to
check them to make sure that you have a configuration that you expect
Mike
- Next message: Vahid: "Re: problem after patching openssh 3.7.1p2"
- Previous message: Gregor Hoffleit: "Re: Using DynDNS names in authorized_keys"
- In reply to: marco_at_marcosoftware.com: "Plain & Simple . . ."
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]