Bug 1631970
| Summary: | openssh host identification changed - without actually changing | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Yanko Kaneti <yaneti> |
| Component: | crypto-policies | Assignee: | Red Hat Crypto Team <crypto-team> |
| Status: | CLOSED ERRATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | unspecified | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | rawhide | CC: | code, crypto-team, jjelen, kevin, lef, leftmostcat, mailinglists35, nmavrogi, tmraz |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | crypto-policies-20180925-1.git71ca85f.fc29 | Doc Type: | If docs needed, set a value |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2018-09-27 18:01:28 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
|
Description
Yanko Kaneti
2018-09-22 16:37:03 UTC
Forgot to mention that I have two different hosts with ecdsa-sha2-nistp256 keys exhibiting the same problem , one Fedora , the other Junos. So I'd assume its not a server misconfiguration problem. Please consider that even if the policy change would require changing the previously used keys the user experience of warnings about host identity changing is not at all optimal. You might want to throw this to openssh. This is related to the https://gitlab.com/redhat-crypto/fedora-crypto-policies/merge_requests/28/ Without the explicit specification of the algorithm list, OpenSSH client will prefer the host key algorithms that it has the known hosts for. The new explicit ordering prefers RSA keys and ECDSA and ED25519 are after that. I am not sure about other protocols (TLS), but I assume that elliptic curves should come before RSA, if there is no good reason for the opposite ordering. this change is disruptive. please revert. do your defaults for *NEW* connections but please *DO*NOT* BREAK existing saved keys, because I wasted time searching for potential wifi hijackers until I found this issue. please don't go with this state in fedora release using fc29 here if you put this in release you will get torrents of floods of thousands angry innocent users. and that's bad for your karma. meanwhile workaround: 1. grep your saved host in ~/.ssh/known_hosts 2. extract the second field 3. ssh -o HostKeyAlgorithms=$(value from step 2) user@host crypto-policies-20180925-1.git71ca85f.fc29 has been submitted as an update to Fedora 29. https://bodhi.fedoraproject.org/updates/FEDORA-2018-95580e520c This change is incredibly disruptive and should be reverted. It is reverted in the update in comment 8. crypto-policies-20180925-1.git71ca85f.fc29 has been pushed to the Fedora 29 testing repository. If problems still persist, please make note of it in this bug report. See https://fedoraproject.org/wiki/QA:Updates_Testing for instructions on how to install test updates. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2018-95580e520c crypto-policies-20180925-1.git71ca85f.fc29 has been pushed to the Fedora 29 stable repository. If problems still persist, please make note of it in this bug report. |