Clearing PuTTY's Cache Of Host Finger Prints On Windows OS Event Sources
Originally Published: 2017-01-30
Last Modified: 2023-09-22
Article Number
Applies To
RSA Product/Service Type: SA Log Collection
RSA Version/Condition: 10.4.X,10.5.X,10.6.X
Issue
Received below error for sasftpagent -v command:
The server's host key does not match the one PuTTY has
cached in the registry. This means that either the server administrator has changed the host key, or you have actually connected to another computer pretending to be the server.
The new rsa2 key fingerprint is:
ssh-rsa 2048 23:59:f5:ca:ca:50:a9:0a:42:08:26:0e:4b:69:0b:56
Connection abandoned.
Cause
Resolution
1. Open the registry (regedit)
2. Go to HKEY_CURRENT_USER\Software\SimonTatham\PuTTY\SshHostKeys
3. Select SshHostKeys , right click and export.(This is for backup)
4. There you should see Putty’s cache of host keys.
The ‘name’ column tells you which key is for which server.
For example, it will have the format of @: [rsa2@22:YourhostIP]
5. Delete the rows that you need.
6. Regenerate the SSH keys and update into LC/VLC
7. Refer below Link to generate the SSH keys
https://community.rsa.com/docs/DOC-53125
Related Articles
AFX Connector Stays in Stopped state 21Number of Views RSA Identity Governance and Lifecycle 7.1.0.6 Release Notes 20Number of Views Weblogic agent (identity asserter) does not allow cookie name other than CTSESSION 21Number of Views RSA Identity Governance & Lifecycle - Access Certification whitepaper 73Number of Views Difference between a Delegate Reviewer and Alternate Manager in Access Certifications using Identity Governance & Lifecycle 39Number of Views
Trending Articles
RSA Authentication Manager 8.9 Patches and Hotfixes Readme RSA MFA Agent 2.5 for Microsoft Windows Installation and Administration Guide RSA Authentication Manager Patch Updates RSA Authentication Manager Upgrade Process RSA-2026-24: RSA Authentication Manager Security Update for Third-Party Component Vulnerabilities
Don't see what you're looking for?