If you are going through a socks proxy there are many noted problems with
ssh clients and socks. It seems that there has been trouble synchronizing
the changes in versions of each. I have exactly the problem described below
- only it fails on reverting to rsh - and yet I have no problem with my
windows ssh client from another machine, or with, say, rtelnet.
Blaaaaghgh!
> -----Original Message-----
> From: Harry Putnam [mailto:[EMAIL PROTECTED]]
> Sent: Monday, July 19, 1999 8:08 PM
> To: Mike A. Harris
> Cc: Rohit Dhamankar; [EMAIL PROTECTED]
> Subject: Re: ssh ??
>
>
> "Mike A. Harris" <[EMAIL PROTECTED]> writes:
>
> > On Wed, 14 Jul 1999, Rohit Dhamankar wrote:
> >
> > >Hi,
> > >Been trying to set up ssh for my Linux box. I have set my
> keys properly !
> > >The error I get is
> > >Secure connection to blah blah refused; reverting to
> insecure method
> > >and it goes to rsh
> > >
> > >scp does not work;
> > >Anybody has a clue ??
> >
> > You must be using the same version of ssh on both machines. Run
> > ssh-keygen from each account you wish to use to login to a remote
> > machine. Do not use a passphrase when generating the keys.
> >
> > Then upload your identity.pub file renamed to authorized_keys
> > into the .ssh dir on the remote machine. Make sure the
> > permissions on it are 600.
>
> That is the kind of behavior you see when sshd isn't running on one
> machine. You might check to make sure sshd is running on both.
>
>
>
>
