Your message dated Wed, 18 Jan 2017 01:03:55 +0000
with message-id
<1484701435.2699191.851084080.0efc4...@webmail.messagingengine.com>
and subject line Re: python-paramiko doesn't work with python-crypto 2.6-4
has caused the Debian Bug report #850077,
regarding python-paramiko doesn't work with python-crypto 2.6-4
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
850077: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=850077
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: duplicity
Version: 0.6.18-3
Severity: grave
Justification: renders package unusable
Dear Maintainer,
Since yesterday's update, backup to a SSH target is broken and leads to this
stacktrace:
ssh: Unknown exception: CTR mode needs counter parameter, not IV
ssh: Traceback (most recent call last):
ssh: File "/usr/lib/python2.7/dist-packages/paramiko/transport.py", line
1542, in run
ssh: self.kex_engine.parse_next(ptype, m)
ssh: File "/usr/lib/python2.7/dist-packages/paramiko/kex_group1.py", line 68,
in parse_next
ssh: return self._parse_kexdh_reply(m)
ssh: File "/usr/lib/python2.7/dist-packages/paramiko/kex_group1.py", line
107, in _parse_kexdh_reply
ssh: self.transport._activate_outbound()
ssh: File "/usr/lib/python2.7/dist-packages/paramiko/transport.py", line
1831, in _activate_outbound
ssh: engine = self._get_cipher(self.local_cipher, key_out, IV_out)
ssh: File "/usr/lib/python2.7/dist-packages/paramiko/transport.py", line
1480, in _get_cipher
ssh: return self._cipher_info[name]['class'].new(key,
self._cipher_info[name]['mode'], iv, counter)
ssh: File "/usr/lib/python2.7/dist-packages/Crypto/Cipher/AES.py", line 94,
in new
ssh: return AESCipher(key, *args, **kwargs)
ssh: File "/usr/lib/python2.7/dist-packages/Crypto/Cipher/AES.py", line 59,
in __init__
ssh: blockalgo.BlockAlgo.__init__(self, _AES, key, *args, **kwargs)
ssh: File "/usr/lib/python2.7/dist-packages/Crypto/Cipher/blockalgo.py", line
141, in __init__
ssh: self._cipher = factory.new(key, *args, **kwargs)
ssh: ValueError: CTR mode needs counter parameter, not IV
*** Please consider answering these questions, where appropriate ***
* What led up to the situation?
The upgrade of python-crypto from 2.6-4+deb7u3 to 2.6-4+deb7u4
* What exactly did you do (or not do) that was effective (or
ineffective)?
I did a downgrade of python-crypto to 2.6-4+deb7u3.
* What was the outcome of this action?
My backups are working again.
* What outcome did you expect instead?
*** End of the template - remove these lines ***
-- System Information:
Debian Release: 7.11
APT prefers oldstable-updates
APT policy: (500, 'oldstable-updates'), (500, 'oldstable')
Architecture: amd64 (x86_64)
Kernel: Linux 3.10.23-xxxx-std-ipv6-64 (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages duplicity depends on:
ii libc6 2.13-38+deb7u11
ii librsync1 0.9.7-9
ii python 2.7.3-4+deb7u1
ii python-gnupginterface 0.3.2-9.1
Versions of packages duplicity recommends:
ii python-paramiko 1.7.7.1-3.1
ii rsync 3.0.9-4
Versions of packages duplicity suggests:
pn lftp <none>
ii ncftp 2:3.2.5-1.1
pn python-boto <none>
pn python-cloudfiles <none>
ii python-gdata 2.0.17+dfsg-1
ii python-pexpect 2.4-1
pn tahoe-lafs <none>
-- no debconf information
--- End Message ---
--- Begin Message ---
Version: 2.6-4+deb7u7
Hi,
> python-paramiko doesn't work with python-crypto 2.6-4
I believe this was fixed in 2.6-4+deb7u7 (or earlier). :)
Regards,
--
,''`.
: :' : Chris Lamb
`. `'` la...@debian.org / chris-lamb.co.uk
`-
--- End Message ---
