Change: Add workaround for non-standard SSH ports #925
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What:
This PR is to address #924
I don't think this is the most elegent solution - it would be preferable to use Paramiko's handling of non-standard ports, but TBH, I can't decypher how they are doing it right now.
For now, this PR includes the workaround I've built to get my solution working.
What I don't think this PR will solve is hashed or salted hostnames.
Why:
To allow SSHConnection to connect on non-standard ports and store/resuse known_host entries.
How:
I've used local edits per the PR. Verfied using the script referenced in #924.
I've confirmed:
Checklist: