dev-python/paramiko: apply iqmp-swap patch #17309
Closed
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.
Apply this upstream patch to allow
duplicity
to work correctly with theparamiko
backend, when performing backups over sftp. Otherwise it fails with the errorBackendException: ssh connection to <user>@<addr>:22 failed: ('Invalid private key', [_OpenSSLErrorWithText(code=67764350, lib=4, func=160, reason=126, reason_text=b'error:040A007E:rsa routines:RSA_check_key_ex:iqmp not inverse of q')])
I noticed this issue when my periodic duplicity backup via sftp using the
paramiko
backend started failing as of 2020-08-28. The upstream patch fixing the issue, and included in this pull request, was committed around the same time.I do not know the cause of the breakage, but this patch does resolve the issue. Tested both with user patches and in an ~amd64 container.
EDIT: as acknowledged in the upstream patch message this breakage may be related to
dev-python/cryptography
, which upgraded on my system to version 3.1 on the same day the above error began.