BUG: When using SSH TUNNEL option host fingerprints aren't saved

Using last nightly build, when using the SSH TUNNEL option (Jump Host proxy) the target host fingerprint is not stored even you select to do it.

Expected Behavior

When selecting YES to store the fingerprint then the next time you connect to this server it's needed to be known.

Current Behavior

Every time you connect to the server you see that the fingerprint is not known.

Possible Solution

You need to fix the error checking if the correct fingerprint is stored.

Steps to Reproduce (for bugs)

1. Create a new SSH connection using the SSH TUNNEL option.
2. Connect to the server and pass the login of the jump server.
3. When connecting to the target server, in the window asking about the fingerprint select YES.
4. Close the connection and restart it... you will return to see the fingerprint window.

Context

This bug appears in the last nightly build that includes the SSH TUNNEL functionality.

Your Environment

• Version used: 1.77.2.41427
• Operating System and version (e.g. Windows 10 1709 x64): Windows 10 21H1 Home 64bit

Start by reproducing the SSH TUNNEL connection described in the issue and trace where the target host fingerprint is checked and stored after selecting YES. Confirm the fix by closing and restarting the connection and verifying that the fingerprint prompt no longer appears.