On Thu, 25 Oct 2001, Steven J. Yellin wrote:
> On Thu, 25 Oct 2001, Frank Tanner III wrote:
>
> > I know I am going to feel like a dumbass when I get the answer,
> > because I have probably overlooked something very basic, but here
> > goes.
> >
> > I am trying to automate the scp'ing of a file from one server to
> > another. On the computer that the scp command will be executing on, I
> > have issued the ssh-keygen command and followed the on-screen prompts.
> > I, then, copied the identity.pub to the sending computer under the
> > ~/.ssh/authorized_keys file. This doesn't appear to work. I still
> > get prompted for a password. Both user accounts have the same
> > password. What am I over looking?
>
> I assume you're using openssh. In that case, without the -t parameter
> of ssh-keygen, you generate identity.pub, which is appropriate for
> protocol version 1. With the -t, you get id-rsa.pub, which should be put
> in authorized_keys2 for use with protocol version 2. When you use ssh
> or scp, the /etc/ssh/ssh*_config files are probably at default "Protocol
> 2,1" so that unless you say otherwise, protocol 2 is used.
>
If you still have problems, make sure the the authorized_keys and
authorized_keys2 files are not group or world writable. If they are,
openssh will not use them.
Mikkel
--
Do not meddle in the affairs of dragons,
for you are crunchy and taste good with ketchup.
_______________________________________________
Seawolf-list mailing list
[EMAIL PROTECTED]
https://listman.redhat.com/mailman/listinfo/seawolf-list
