New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
avoid KeyError when canonicaldomains is missing #2338
base: main
Are you sure you want to change the base?
Conversation
paramiko assumes that `canonicaldomains` is always present when `CanonicalizeHostname` is set, and it errors out when it is not, preventing the whole host config from being parsed. Xpra-org/xpra#3868 (comment)
It would be good to add a test case for the bugged situation here, to guard against future regression -- is that something you could tackle, @totaam? Also, we'll want a CHANGELOG entry for this -- please add a bullet to Thanks for this! |
I can take a look, not sure when. |
No worries on timeline, @totaam, happy to take care of this whenever you're able. |
paramiko assumes that `canonicaldomains` is always present when `CanonicalizeHostname` is set, and it errors out when it is not, preventing the whole host config from being parsed. Xpra-org/xpra#3868 (comment)
The updated PR adds a test which verifies that paramiko no longer blows up when a config specifies The failing check is not related to the changes I made so I am ignoring it. |
Please review this PR, the failing test is not caused by it. |
paramiko assumes that
canonicaldomains
is always present whenCanonicalizeHostname
is set, and it errors out when it is not, preventing the whole host config from being parsed.Xpra-org/xpra#3868 (comment)