-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
fortinet _preferred_kex settings interfering with other devices #3530
Conversation
CC: Noppes |
@Noppes I changed the logic a little bit and added some tests, I think it should all work the same, but let me know if you see any issues (and we can fix). |
in your change it looks like now self.disabled_algorithms can be None, while in the original it was always an empty dict then. Otherwise looks good 👌 |
Yes that is correct as None is the default in Paramiko
Kirk
On Sun, Nov 10, 2024 at 7:48 AM Noppes ***@***.***> wrote:
CC: Noppes <https://github.com/Noppes>
in your change it looks like now self.disabled_algorithms can be None,
while in the original it was always an empty dict then
—
Reply to this email directly, view it on GitHub
<#3530 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAG3VBFP5MA2IVEFE3EKEC3Z7556XAVCNFSM6AAAAABROBOOIGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDINRWG44DIOBXGU>
.
You are receiving this because you modified the open/close state.Message
ID: ***@***.***>
--
Kirk Byers
***@***.***
Simplify through Automation
* <https://pynet.twb-tech.com>*
|
Basically, we shouldn't change the value from the Paramiko default unless we are actually doing something with the variable. |
No description provided.