We have 2 Windows 2003 Servers that were upgraded from WinSSHD 4.15a to 5.03 last night. They immediately began having trouble when clients were connecting to them:
debug3: Not a RSA1 key file /home/account/.ssh/id_rsa.
debug2: key_type_from_name: unknown key type '-----BEGIN'
debug3: key_read: missing keytype
debug3: key_read: missing whitespace
On our systems, this particular account has the same .ssh keys -- our other systems that are running 5.03 are working fine. So, my question is, what could have happened during the update that would have caused this problem. I'm fairly certain it's not a public key format issue (we use OpenSSH from our Redhat systems) - they work fine on other systems.
Thank you for reporting this!
Though I must say I cannot make any conclusions.
The problem with RSA1 key decoding has occurred on your SSH client. Your SSH client is suggesting that the local /home/account/.ssh/id_rsa file is invalid. WinSSHD could not have corrupted that file - it is not even running on computer storing that file.
I would need to see WinSSHD file logs to see what has happened exactly. The complete client's debug log wouldn't hurt either.
If you can find time to find logs, and if you are willing to send it over, then please send it to me directly by clicking mail icon next to my name. If you want, you can also edit information that you may find sensitive (IPs, usernames).
Btw. has your upgrade right expired? Is that why you've downgraded from 5.05 to 5.03? Because otherwise it wouldn't make much sense to use the older WinSSHD version.
This topic is archived. No further replies will be accepted.Other recent topics