Hi again,
Well as mentioned yesterday, I couldn't let this one go by without at
least trying to figure out the real reason, so I experimented somewhat
further.
The issue of ssh1 vs. ssh2 appears to already be clarified, so I won't
go into it again.
Yes, indeed. I myself yesterday came to
Hi all,
To cut to the chase, I 'solved' the issue, or rather, the mystery around
it at least, but the 'solution' was not quite as expected.
I tried both suggestions given.
Firstly:
It rather looks like putty is checking the server key with the older one
(you mentioned you reinstalled the
In response to Olaf Greve [EMAIL PROTECTED]:
To cut to the chase, I 'solved' the issue, or rather, the mystery around
it at least, but the 'solution' was not quite as expected.
I tried both suggestions given.
Firstly:
It rather looks like putty is checking the server key with the
Hi Bill,
I'm not seeing this. I tried this with PuTTY 0.58 on a fresh FreeBSD 6.2p1
system and had no problems. So I grabbed the latest PuTTY 0.59, and that
worked fine as well.
[...]
I haven't been following this thread, so I don't have any ideas on what
your problem might be, but it's
Hi again,
I must ammend a technically incorrect thing that I wrote previously:
Is this what you tried too, or did you use SSH2 (i.e. key
authentication, instead of password authentication)?
Both SSH1 and SSH2 can use password authentication, so I incorrectly
wrote that PuTTY does not fall
Olaf Greve wrote:
The issue is that PuTTY does not fall back from its SSH2 attempt to
SSH1 (with password authentication), as is what I specified in my
/etc/ssh/sshd_config
Is this what you tried too, or did you use SSH2 (i.e. key
authentication, instead of password authentication)?
Olaf Greve wrote:
Hi guys,
The question:
I recall having had this issue before, and I *think* the resolution was
to enable PAM authentication or so outside of /etc/ssh/sshd_config. I
thought to recall that I either did this in rc.conf (or the defaults for
that), or in the custom
