On Mon, 7 Jan 2002 03:06:39 -0500
Daniel Freedman <[EMAIL PROTECTED]> wrote:
> Not sure exactly what's going on here, maybe you just have some config
> option specifying this in sshd_config, but, according to the release
> notes on openssh.org, for version 3.0 of openssh, authorized_keys2 is
> now
On Mon, Jan 07, 2002, Patrick Hsieh wrote:
> > > In Debian A, I ssh-keygen the public key, scp and append to Debian B
> > > ~/.ssh/authorized_keys
> >
> > It seems that Debian now uses protocol version 2, so maybe you need to
> > add v2 key to ~/.ssh/authorized_keys2.
> >
>
> Thanks. I end up wi
> > In Debian A, I ssh-keygen the public key, scp and append to Debian B
> > ~/.ssh/authorized_keys
>
> It seems that Debian now uses protocol version 2, so maybe you need to
> add v2 key to ~/.ssh/authorized_keys2.
>
> --
> Alexey
>
> "Python is executable pseudocode, Perl is executable line-n
> In Debian A, I ssh-keygen the public key, scp and append to Debian B
> ~/.ssh/authorized_keys
It seems that Debian now uses protocol version 2, so maybe you need to
add v2 key to ~/.ssh/authorized_keys2.
--
Alexey
"Python is executable pseudocode, Perl is executable line-noise."
Hello list,
I have to Debian woody with ssh-3.0.1p1-1.2.
In Debian A, I ssh-keygen the public key, scp and append to Debian B
~/.ssh/authorized_keys
Then I try to ssh login from Debian A to Debian B again, but still got
the password prompt.
Is there something wrong?
--
Patrick Hsieh <[EMAIL PR
5 matches
Mail list logo