Re: libgcrypt11 same issue? Was: Re: [SECURITY] [DLA 1283-1] python-crypto security update

2018-04-12 Thread Ola Lundqvist
Hi Yes I forgot to push my changes. Thanks for handling it for me. // Ola On 12 April 2018 at 14:14, Ola Lundqvist wrote: > Hi > > I thought I did. Maybe I forgot to push my changes. > > Thanks for resolving it. > > // Ola > > On 11 April 2018 at 22:18, Antoine Beaupré > wrote: > >> On 2018-0

Re: libgcrypt11 same issue? Was: Re: [SECURITY] [DLA 1283-1] python-crypto security update

2018-04-12 Thread Ola Lundqvist
Hi I thought I did. Maybe I forgot to push my changes. Thanks for resolving it. // Ola On 11 April 2018 at 22:18, Antoine Beaupré wrote: > On 2018-04-10 14:33:28, Ola Lundqvist wrote: > > Hi Salvatore > > > > Great. Thanks. Then we do not need to do anything more to libgcrypt. I'll > > remove

Re: libgcrypt11 same issue? Was: Re: [SECURITY] [DLA 1283-1] python-crypto security update

2018-04-11 Thread Antoine Beaupré
On 2018-04-10 14:33:28, Ola Lundqvist wrote: > Hi Salvatore > > Great. Thanks. Then we do not need to do anything more to libgcrypt. I'll > remove it from dla-needed.txt. Assuming you forgot to do so, I went ahead and removed it from dla-needed.txt and marked it as no-dsa in wheezy. A. -- Argui

Re: libgcrypt11 same issue? Was: Re: [SECURITY] [DLA 1283-1] python-crypto security update

2018-04-10 Thread Ola Lundqvist
Hi Salvatore Great. Thanks. Then we do not need to do anything more to libgcrypt. I'll remove it from dla-needed.txt. // Ola On 9 April 2018 at 21:06, Salvatore Bonaccorso wrote: > Hi Ola, > > On Mon, Apr 09, 2018 at 08:59:32PM +0200, Ola Lundqvist wrote: > > Hi all > > > > I found another iss

Re: libgcrypt11 same issue? Was: Re: [SECURITY] [DLA 1283-1] python-crypto security update

2018-04-09 Thread Salvatore Bonaccorso
Hi Ola, On Mon, Apr 09, 2018 at 08:59:32PM +0200, Ola Lundqvist wrote: > Hi all > > I found another issue that looks very similar. It is > https://security-tracker.debian.org/tracker/CVE-2018-6594 > > Should we treat it the same way, marking it as ignored? I guess you mean CVE-2018-6829? If so

libgcrypt11 same issue? Was: Re: [SECURITY] [DLA 1283-1] python-crypto security update

2018-04-09 Thread Ola Lundqvist
Hi all I found another issue that looks very similar. It is https://security-tracker.debian.org/tracker/CVE-2018-6594 Should we treat it the same way, marking it as ignored? Best regards // Ola On 9 April 2018 at 07:26, Salvatore Bonaccorso wrote: > Hi Brian, > > On Fri, Apr 06, 2018 at 07:0