Closed fuzzmonkey closed 1 year ago
In Postico 2, the fingerprint is shown in the connection settings. Clearing the field should fix the problem.
I don't want to make resetting the fingerprint too convenient, since I want people to stop and think when this happens.
But maybe I should make an exception when the new key is already in the known_hosts file.
hey @jakob - thanks for the rapid response! That did indeed fix the problem. I hadn't noticed the fingerprint in connection settings.
But maybe I should make an exception when the new key is already in the known_hosts file.
That would be ideal. Our bastion box gets replaced on most terraform runs, so this happens a lot. At least i know how to fix it going forward!
What did you do?
Attempted to connect to a database via a bastion box after the bastion box has changed.
What did you expect to happen?
An option to replace/update the key. IIRC this issue was fixed in v1.x
What actually happened?
I just see
The ECDSA host key of the SSH server did not match the fingerprint.
What software versions are you using?
Postico version: 2.0.1 macOS version: 13.3.1 (22E261) PostgreSQL version: 14.7