On Fri, Jan 06, 2017 at 01:53:47PM +0100, Sebastian Ramacher wrote:
> It was fixed in 2-6-4+deb7u6.
Thanks, I can confirm that this fixes the problem.
> Then perhaps the discussions you read are wrong or incomplete. Maybe there is
> no
> exploitable code out there using CTR mode, but it can be
Hi Zed
On 2017-01-05 16:53:44, Zed Pobre wrote:
> On Wed, Jan 04, 2017 at 01:14:19PM +0100, Sebastian Ramacher wrote:
> > On 2017-01-03 13:07:38, Zed Pobre wrote:
> > > Despite that, I think I agree that paramiko needs to change. The
> > > problem is that this is a stable distribution, and the pa
On Wed, Jan 04, 2017 at 01:14:19PM +0100, Sebastian Ramacher wrote:
> On 2017-01-03 13:07:38, Zed Pobre wrote:
> > Despite that, I think I agree that paramiko needs to change. The
> > problem is that this is a stable distribution, and the patch that
> > causes this problem, used to fix #849495, is
On 2017-01-03 13:07:38, Zed Pobre wrote:
> I'm also having this problem. Some searching shows that the pycrypto
> folks believe that this should be fixed in paramiko:
>
> https://github.com/dlitz/pycrypto/issues/149
>
> A fellow who found a workaround on the paramiko side notes that the
> pycr
I'm also having this problem. Some searching shows that the pycrypto
folks believe that this should be fixed in paramiko:
https://github.com/dlitz/pycrypto/issues/149
A fellow who found a workaround on the paramiko side notes that the
pycrypto comments in AES.py are wrong now:
http://uucod
5 matches
Mail list logo