last call for KRACK update on wheezy

2017-10-30 Thread Antoine Beaupré
I have heard positive comments in private about the binary packages supplied: apparently, they work, but no one has been able to test them against an actual attack yet. I have also done some smoke tests myself and things generally seem to work. So I will probably upload the binaries tomorrow if

Re: Version number for the next quagga update

2017-10-30 Thread Chris Lamb
Hi Hugo, > I'm currently preparing the next quagga update, but found out that the > current version number of quagga in wheezy is pretty unusual: > > 0.99.22.4-1+wheezy3+deb7u1 […] > Is there a specific reason for that ? No, it was an accident on my part. Presumably blindly calling dch without

Re: Version number for the next quagga update

2017-10-30 Thread Markus Koschany
Am 30.10.2017 um 16:47 schrieb Hugo Lefeuvre: > Hi, > > I'm currently preparing the next quagga update, but found out that the > current version number of quagga in wheezy is pretty unusual: > > 0.99.22.4-1+wheezy3+deb7u1 > > I'd have expected it to be 0.99.22.4-1+wheezy4. > > Is there a

Version number for the next quagga update

2017-10-30 Thread Hugo Lefeuvre
Hi, I'm currently preparing the next quagga update, but found out that the current version number of quagga in wheezy is pretty unusual: 0.99.22.4-1+wheezy3+deb7u1 I'd have expected it to be 0.99.22.4-1+wheezy4. Is there a specific reason for that ? Since 0.99.22.4-1+wheezy3+deb7u1 <

October Report

2017-10-30 Thread Hugo Lefeuvre
Hi, October 2017 was my 14th month as a payed Debian LTS contributor. I was allocated 20 hours. I have spent all of them doing the following tasks: * Organize libav support in Wheezy, test and upload libav update 6:0.8.21-0+deb7u1 (DLA 1142-1). Despite the higher activity around libav LTS

Re: Wheezy update of suricata?

2017-10-30 Thread Arturo Borrero Gonzalez
On 27 October 2017 at 20:06, Thorsten Alteholz wrote: > Dear maintainer(s), > > The Debian LTS team would like to fix the security issues which are > currently open in the Wheezy version of suricata: > https://security-tracker.debian.org/tracker/source-package/suricata > >

Re: Heads-up CVE-2017-16227/quagga

2017-10-30 Thread Hugo Lefeuvre
Hi Salvatore, > In case LTS team is interested in releasing a DLA for > CVE-2017-16227/quagga: The patch has been tested as well for the > wheezy version and solves the problem. > > Info: https://security-tracker.debian.org/CVE-2017-16227 and > corresponding https://bugs.debian.org/879474 .

Heads-up CVE-2017-16227/quagga

2017-10-30 Thread Salvatore Bonaccorso
Hi In case LTS team is interested in releasing a DLA for CVE-2017-16227/quagga: The patch has been tested as well for the wheezy version and solves the problem. Info: https://security-tracker.debian.org/CVE-2017-16227 and corresponding https://bugs.debian.org/879474 . Regards, Salvatore

Re: Wheezy update of icedove?

2017-10-30 Thread Moritz Mühlenhoff
On Mon, Oct 30, 2017 at 08:06:27AM +0100, Guido Günther wrote: > I've seen preparation mails for Stretch and Jessie. Is there anything > missing that I can help with? The stretch version is in NEW due to the rename and needs FTP master processing. jessie is ready. Cheers, Moritz

Re: Wheezy update of icedove?

2017-10-30 Thread Guido Günther
Hi Carsten, On Fri, Oct 20, 2017 at 01:06:09PM +0200, Guido Günther wrote: > Hi Carsten, > On Tue, Oct 17, 2017 at 09:05:38PM +0200, Carsten Schoenert wrote: > > Am 15.10.2017 um 23:24 schrieb Guido Günther: > > > Hi Carsten, > > > On Sun, Oct 15, 2017 at 09:46:15PM +0200, Carsten Schoenert wrote: