On 25 Mar 2001, at 10:24, Krzys Majewski wrote:
> it gives "1.99", that probably means the daemon is capable of ssh2.
> Make sure you have a host DSA key (/etc/ssh/host_key or whatever) and
> a user DSA key (~/.ssh/identity or whatever).
It does say 1.99 - and I am proud to say that installing li
Not sure what's going on.. have you tried regenerating your personal
rsa and/or dsa keys (with ssh-keygen)? It looks like your keys are
being rejected for whatever reason.. if you can fix this, it would at
least pare down the number of errors. If you telnet to port 22 on the
remote box, doe
On 23 Mar 2001, at 20:52, Krzys Majewski wrote:
> What happens if you ssh -v -v -v to both the good machine and the bad
> machine? The output below suggests that the bad machine is choking on
> both your rsa key and your dsa key. The good machine only chokes on
> the dsa key, so maybe it's us
What happens if you ssh -v -v -v to both the good machine and the bad
machine? The output below suggests that the bad machine is choking on
both your rsa key and your dsa key. The good machine only chokes on
the dsa key, so maybe it's using whatever rsa key you give it (and
perhaps this is
Well, I finally got something different.
I upgraded to 2.5.2p2 and rebuilt everything. Very good, ./sshd -ddd -
p 9xxx gets me this on the working machine:
debug1: Seeding random number generator
debug1: sshd version OpenSSH_2.5.2p2
debug1: load_private_key_autodetect: type 0 RSA1
debug3: Bad RSA1
5 matches
Mail list logo