Paramiko > 3.4.1 cause to SSH session not active #905
Merged
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
ebattat
force-pushed
the
paramiko_issue
branch
from
2ac2202
to
13bcf6d
Compare
|
I suspect that you're using an old ssh key based on an outdated algorithm. You should update the key. |
|
@RobertKrawitz, |
|
You can try, but I suspect that the issue is that the ssh key you're using relies on an outdated algorithm and that it's behaving as intended. Are you using a fixed ssh key from somewhere? |
|
@RobertKrawitz, Open paramiko issue |
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.
Type of change
Note: Fill x in []
Description
Paramiko 3.4.0 causes the following warning:
/root/benchmark-runner/venv/lib/python3.12/site-packages/paramiko/pkey.py:100: CryptographyDeprecationWarning: TripleDES has been moved to cryptography.hazmat.decrepit.ciphers.algorithms.TripleDES and will be removed from this module in 48.0.0.After upgrading to Paramiko 3.4.1/3.5.0, the following error occurs when running a remote shell:
Got SSH session not active
When revert back to paramiko==3.4.0 all working properly.
Currently, I am using filterwarnings to temporarily suppress the warning and adding a TODO to follow up on the Paramiko fix.
For security reasons, all pull requests need to be approved first before running any automated CI