Bug#1071675: duplicity: SSH broken with Paramiko 3.4

[Alexander Zangerl]

tags 1071675 +moreinfo +unreproducible
severity 1071675 normal
thanks

When trying to do backup to an sftp:// target Duplicity fails since
python3-paramiko was updated to 3.4.0-1, with the following error which

i cannot reproduce this problem. please provide the output of a
duplicity -v9 run and the ssh key types involved on your target machine.

regards
az

[tony mancill]

Post by Alexander Zangerl
tags 1071675 +moreinfo +unreproducible
severity 1071675 normal
thanks

When trying to do backup to an sftp:// target Duplicity fails since
python3-paramiko was updated to 3.4.0-1, with the following error which

i cannot reproduce this problem. please provide the output of a
duplicity -v9 run and the ssh key types involved on your target machine.

Hi,

It's happening here too, for backups using an ed25519 SSH key that has
worked with duplicity in the past. The same key works correctly with
the backend via openssh-client. If it makes a difference, the ssh
server is rsync.net.

Requested debug output attached. Thank you for taking a look. (I think
the severity should be important; duplicity fails for one of its primary
use cases.)

Thanks,
tony

[Alexander Zangerl]

reassign 1071675 python3-paramiko 3.4.0-1
retitle 1071675 "paramiko: ed25519 broken"
tags 1071675 -moreinfo -unreproducible +upstream
thanks

Post by tony mancill
It's happening here too, for backups using an ed25519 SSH key that has
worked with duplicity in the past.

thanks for the debug output, that has indeed helped.

as far as i can tell that's a bug in paramiko, which was reported
late last year:
https://github.com/paramiko/paramiko/issues/2320

i'm therefore reassigning this bug to the paramiko package.

Post by tony mancill
(I think
the severity should be important; duplicity fails for one of its primary
use cases.)

i disagree, because the ssh/sftp backend is just one of many, and there
is a workaround (the pexpect+sftp backend).

regards
az

[tony mancill]

Source: paramiko
Version: 3.4.1-1
Followup-For: Bug #1071675

Please consider the attached patch for the next upload of paramiko. I
have confirmed that it addresses the issue reported using Duplicity in
conjunction with rsync.net.

Alternatively, I could prepare an NMU for this patch if that is
preferred.

Thank you,
tony