fortinet _preferred_kex settings interfering with other devices #3463
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Need to factor in interaction with this: Which I can probably do. |
|
Any status update? |
|
I will try to work on this on Friday (alternative, feel free to reconcile the two items i.e. this PR and linked/referenced item). |
|
Like that? |
|
Superseded by #3530 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
I have a program that connects to multiple devcies, which include fortinet and aruba_os. The moment I connected to a fortinet device I could no longer connect to aruba_os, with the error
paramiko.ssh_exception.IncompatiblePeer: Incompatible ssh peer (no acceptable kex algorithm).Turns out the fortinet driver is editing the paramiko Transport class. This commit fixes that by using
disabled_algorithmsinstead.