Creative Commons Attribution-Noncommercial 3.0 United States License. I have more details here if you are interested.ī If you do forensics on Windows machines, be aware that these registry keys are not only used by PuTTY, but also by FileZilla’s fzsftp.exe module. You can see the registry keys here in FileZilla’s source code: Long story short: I had removed SSH fingerprints cached by PuTTY in the Windows registry, and this impacted FileZilla: both use the same registry keys for their fingerprint cache. I did not go through with the connection, and started to investigate what was going on.

I wanted to transfer some files over SSH with FileZilla, and received a prompt that the server I usually connect to, had an unknown fingerprint. This happened to me a couple of months ago. And then you can decide what to do: continue with the connection, or stop and try to figure out what is going on. This can serve as a safety mechanism: you get a warning when the server you want to connect to, has no longer the same fingerprint. (Im not quite sure how SSH keys work, but I have used them before just like Im. FileZilla got connected easily with the private key and password, but when I tried to use it in the console, the password was not allowed. Many SSH clients can remember SSH servers’ fingerprints. For Public key authentication to work, FileZilla needs to know the private key. I generated an SSH key using WebHost Managers 'Manage roots SSH keys to be used on SFTP and console SSH connection'.

Filezilla ssh key windowa