Unknown Fingerprint

[theologyco]

I have been using Cyberduck on the same computer (MacBookPro wirh OS 10.13.6) for years and it has always worked perfetly until the last few days I have been getting an "unknown fingerprint:" message which begins "The fingerprint for the ssh-ed25519 . . ." then lists the fingerprint. Itgives me choices deny/allow/always. Two questions:

1. what does this mean? Have I inadvertently changed something? How do I fix it?

and 2. If I say allow can this stop the sftp from working or open a vulnerability?

cheers,

Jeffrey

[tatze96]

The "Unknown Fingerprint" message is usually a safety message that lets you know that Cyberduck doesn't know about this server in combination with the specific fingerprint. You can either allow the fingerprint if you are sure to connect to the right server or deny it if you are unsure. Denying the fingerprint will cause the cancellation of the connection process.

Cyberduck will remember the combination of server and fingerprint and won't show that window again for this server if you tick the checkbox Always before clicking on the Allow button.

[theologyco]

Thankyou Laura, I will click on Always, cheers, Jeffrey

…

On 5 Jan 2024, at 01:41, Laura ***@***.***> wrote: The "Unknown Fingerprint" message is usually a safety message that lets you know that Cyberduck doesn't know about this server in combination with the specific fingerprint. You can either allow the fingerprint if you are sure to connect to the right server or deny it if you are unsure. Denying the fingerprint will cause the cancellation of the connection process. Cyberduck will remember the combination of server and fingerprint and won't show that window again for this server if you tick the checkbox Always before clicking on the Allow button. — Reply to this email directly, view it on GitHub <#15472 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AY6I5J3FZFTQSYPR5MZWU7LYM3BDXAVCNFSM6AAAAABAXRDT46VHI2DSMVQWIX3LMV43SRDJONRXK43TNFXW4Q3PNVWWK3TUHM4DAMJTHAZTE>. You are receiving this because you authored the thread.