Bug#851551:

2017-05-04 Thread Hidden Chain
They fixed it in these two versions: http://www.paramiko.org/changelog.html#1.17.4 http://www.paramiko.org/changelog.html#1.18.2 I would like so much to see this fixed, how I could help?

Bug#851551: Info received (Bug#851551: FutureWarning: CTR mode needs counter parameter, not IV)

2017-01-19 Thread Antonis Christofides
Apparently the error message appears even with --verbosity=error.

Bug#851551: FutureWarning: CTR mode needs counter parameter, not IV

2017-01-19 Thread Antonis Christofides
I'm not an expert, but I don't see much similarity with #850025. The symptoms are different and the versions are different.

Bug#851551: FutureWarning: CTR mode needs counter parameter, not IV

2017-01-19 Thread Olivier Berger
On Mon, Jan 16, 2017 at 09:05:15AM +0200, Antonis Christofides wrote: > > I'm not certain this problem is in duplicity or in python-crypto. Since > yesterday's update to Debian 8.7, all my servers (including the one from which > I'm reporting this) throw this message when running duplicity with -v

Bug#851551: FutureWarning: CTR mode needs counter parameter, not IV

2017-01-16 Thread Sebastian Ramacher
Control: reassign -1 duplicity 0.6.24-1 Control: reassign 851474 duplicity 0.6.24-1 On 2017-01-16 17:39:41, Alexander Zangerl wrote: > reassign 851551 python-crypto > thanks No, this is a bug in duplicity. If you see this warning, duplicity (or whichever part of the its dependencies use python-cr

Bug#851551: FutureWarning: CTR mode needs counter parameter, not IV

2017-01-15 Thread Antonis Christofides
Package: duplicity Version: 0.6.24-1 Severity: normal Hello, I'm not certain this problem is in duplicity or in python-crypto. Since yesterday's update to Debian 8.7, all my servers (including the one from which I'm reporting this) throw this message when running duplicity with -v2: /usr/lib/pyt