Error code 5 when saving rsa2 key

R. Lund - Thu 29/08/2013 22:38:09 CEST +0200

Hi.
When I connect to a server and am asked to accept the server's rsa2 key, I get the following error:

Error: Unable to create file rsa2@22%3Amyserver.com Error code: 5

I'm guessing this means that Kitty for some reason cannot write to the registry, but that's about all I can gather here.

I'm running Windows 7 64bit.

Thanks!

Cyd - Fri 30/08/2013 07:37:22 CEST +0200

Are you using classic or portable mode ?

R. Lund - Fri 30/08/2013 17:03:41 CEST +0200

I'm running version 0.61.1.1p.

I thought it USED to work and then stopped, but I don't remember...

It does still save connection information, just not the rsa2 key.

If this IS the portable version, wouldn't saving be disabled?

Hm, in any case, this version is from 2011 - I probably should look for a newer one - didn't see that it was that old...

... well, installed the newest version, manually added all my saved connections - and it crashes every time I run it, even after I removed all other files out of the Kitty directory. It crashes as soon as the username is entered automatically.

So now the new version no longer says that it cannot save the rsa2 key, however I can't use it at all because it crashes...

Thoughts? :-)

R. Lund - Fri 30/08/2013 17:28:19 CEST +0200

Forgot to mention, newest version I have now is 0.63.0.2.

I had to go back to using my age-old version - I'd rather have the rsa2 error than not being able to use it at all...

Is there something in the registry that I might be able to delete to make the new version work, or am I looking at something else entirely?

Any log file I can send to help with this?

R. Lund - Fri 30/08/2013 17:34:31 CEST +0200

Maybe this will help:

Faulting application name: kitty.exe, version: 0.63.0.0, time stamp: 0x521b6f6c
Faulting module name: msvcrt.dll, version: 7.0.7601.17744, time stamp: 0x4eeaf722
Exception code: 0xc0000005
Fault offset: 0x00018dd2
Faulting process id: 0x1b484
Faulting application start time: 0x01cea595bdc6bfc8
Faulting application path: C:\Program Files (x86)\Kitty2\kitty.exe
Faulting module path: C:\Windows\syswow64\msvcrt.dll
Report Id: ff031357-1188-11e3-9d0e-005056c00008

R. Lund - Fri 30/08/2013 17:48:32 CEST +0200

FYI, installing newer versions of Visual C++ didn't help - started with 2010, then 2013 - same issue.

Cyd - Fri 30/08/2013 19:36:54 CEST +0200

0.63.0.0 and 0.63.0.1 had known memory leak issues, dont use them.
Try the uncompressed version (see web site).
UPX is reported to be buggy on 64bits systems!

R. Lund - Fri 30/08/2013 20:42:10 CEST +0200

Thanks for the answer.

Downloaded newest version uncompressed - same issue.

The old version of Kitty does not crash although I'm guessing it would use the same external libraries, right?

R. Lund - Wed 04/09/2013 14:40:27 CEST +0200

Any other ideas on what I can try?

Ricardo - Fri 24/10/2014 14:11:03 CEST +0200

I was experiencing the same issue and discovered that using the IP address instead of the domain name as `Host Name` resolved the issue. Hope this helps someone else out there!

Skibbi - Sat 25/10/2014 19:22:12 CEST +0200

I had silimar issue on Windows 8.1 x64.
I went to c:\Users\\AppData\Local\VirtualStore\Program Files (x86)\ and deleted kitty folder. After kitty restart it started caching server keys in c:\Program Files (x86)\kitty\SshHostKeys\

Mike - Mon 21/12/2015 23:19:25 CET +0100

I see now why IP address works when domain name doesn't... most domain names end in .COM which is an extension that is used for executable files. As a security precaution windows doesn't allow for creating such files without administrator rights.

I confirmed that I can save keys for .NET host just fine, and changing to IP for a .COM host resolves that particular issue.

Answer

The forum is actually closed