SSH Connection Fingerprint Mismatch
- Dominant language
- Python
- Stars
- 485
- Forks
- 8
- PR merge metrics
- No merged PRs in 30d
Description
Hello! I just upgraded to Sierra and Postico is reporting a ssh fingerprint that's different from the one added to the known_hosts file. I think this has something to do with the newer sha256 hash default.
This is preventing me from connecting to any Postgres DBs via SSH. The solution was copying a saved version of the known_hosts entry from an older backup.
Contributor guide
No contributing guide indexed for this repository
Research direction
No files, tests, or entry points are named. Start by reproducing the SSH connection to a Postgres database on Sierra and compare the fingerprint reported by Postico with the saved known_hosts entry; done means the fingerprint is handled consistently and the connection succeeds without restoring an older entry.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- postgresql, python
- Domain
- databases, networking
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100