-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Tue, 31 Oct 2017 18:49:10 +0100
Source: libdatetime-timezone-perl
Binary: libdatetime-timezone-perl
Architecture: source all
Version: 1:1.58-1+2017c
Distribution: wheezy-security
Urgency: medium
Maintainer: Debian Perl Group
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Tue, 31 Oct 2017 18:08:50 +0100
Source: tzdata
Binary: tzdata tzdata-java
Architecture: source all
Version: 2017c-0+deb7u1
Distribution: wheezy-security
Urgency: medium
Maintainer: GNU Libc Maintainers
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Package: tzdata
Version: 2017c-0+deb7u1
This update includes the changes in tzdata 2017b. Notable
changes are:
- Northern Cyprus resumed EU rules starting 2017-10-29.
- Namibia will switch from +01 with DST to +02 all year,
Package: graphicsmagick
Version: 1.3.16-1.1+deb7u12
CVE ID : CVE-2017-14103 CVE-2017-14314 CVE-2017-14504
CVE-2017-14733 CVE-2017-14994 CVE-2017-14997
CVE-2017-15930
Debian Bug : 87
Multiple vulnerabilities were found in
> The mailing list web archives are being rebuilt, according to
> #debian-lists.
>
> So even though you don't see your message in the web interface, it may
> have actually gone through, SMTP-wise.
>
> Mine (DLA-1150-1, wpa) did, in any case.
Oh, you're right, the web archive is now displaying
On 2017-10-31 15:45:31, Raphael Hertzog wrote:
> On Tue, 31 Oct 2017, Antoine Beaupré wrote:
>> I'll take care of it then. Should I just reuse the old DLA id? or
>> simply mention the old DLA id in the announcement? Or mention all the
>> CVEs fixed in the old DLA in the new DLA?
>>
>> Not
On 2017-10-31 17:40:30, Hugo Lefeuvre wrote:
> Hi,
>
>> In my case, I also previously had issues because I added a new signing
>> subkey that took some time to propagate across Debian's infrastructure.
>>
>> The main issue is we have currently no way of noticing when a number is
>> skipped. It
Hi,
> In my case, I also previously had issues because I added a new signing
> subkey that took some time to propagate across Debian's infrastructure.
>
> The main issue is we have currently no way of noticing when a number is
> skipped. It would be nice to automate this stuff somehow, yet I
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Package: wordpress
Version: 3.6.1+dfsg-1~deb7u17
CVE ID : CVE-2016-9263 CVE-2017-14718 CVE-2017-14719
CVE-2017-14720 CVE-2017-14721 CVE-2017-14722
CVE-2017-14723 CVE-2017-14725
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Package: quagga
Version: quagga_0.99.22.4-1+wheezy3+deb7u2
CVE ID : CVE-2017-16227
Debian Bug : 879474
It was discovered that the bgpd daemon in the Quagga routing suite
does not properly calculate the length of
Package: wpa
Version: 1.0-3+deb7u5
CVE ID : CVE-2017-13077 CVE-2017-13078 CVE-2017-13079 CVE-2017-13080
CVE-2017-13081 CVE-2017-13082 CVE-2017-13086 CVE-2017-13087
CVE-2017-13088
A vulnerability was found in how WPA code can be triggered
On Tue, 31 Oct 2017, Antoine Beaupré wrote:
> I'll take care of it then. Should I just reuse the old DLA id? or
> simply mention the old DLA id in the announcement? Or mention all the
> CVEs fixed in the old DLA in the new DLA?
>
> Not actually sure how to merge this. :)
You prepare your DLA
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Mon, 30 Oct 2017 16:57:40 +0100
Source: quagga
Binary: quagga quagga-dbg quagga-doc
Architecture: source amd64 all
Version: 0.99.22.4-1+wheezy3+deb7u2
Distribution: wheezy-security
Urgency: high
Maintainer: Christian Hammers
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Tue, 31 Oct 2017 15:13:56 +0100
Source: wordpress
Binary: wordpress wordpress-l10n
Architecture: source all
Version: 3.6.1+dfsg-1~deb7u17
Distribution: wheezy-security
Urgency: high
Maintainer: Giuseppe Iuculano
Hi Markus, Chris,
> I think using 0.99.22.4-1+wheezy4 would have been correct in this case
> but I would continue with 0.99.22.4-1+wheezy3+deb7u2 now. In the light
> of our proposed change to reportbug it makes even sense to append
> +deb7u1 because this is the string we are looking for when we
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Mon, 23 Oct 2017 17:09:19 -0400
Source: wpa
Binary: hostapd wpagui wpasupplicant wpasupplicant-udeb
Architecture: source amd64
Version: 1.0-3+deb7u5
Distribution: wheezy-security
Urgency: high
Maintainer: Debian/Ubuntu
On 2017-10-31 14:13:13, Raphael Hertzog wrote:
> On Tue, 31 Oct 2017, Antoine Beaupré wrote:
>> > Please send it again and add a small sentence explaining that you send an
>> > old advisory that never made it to the list... IOW if you expect
>> > confusion, add an explanation to clear it up.
>>
On Tue, 31 Oct 2017, Antoine Beaupré wrote:
> > Please send it again and add a small sentence explaining that you send an
> > old advisory that never made it to the list... IOW if you expect
> > confusion, add an explanation to clear it up.
>
> I will be looking at a GM update later today -
On 2017-10-31 11:56:31, Raphael Hertzog wrote:
> Hi,
>
> On Sat, 28 Oct 2017, Brian May wrote:
>> I didn't realize until after I uploaded the newer version associated
>> with DLA-1140-1. So I tried sending DLA-1130-1 again, followed by
>> DLA-1140-1.
>>
>> Unfortunately DLA-1140-1 made it to the
Hi,
On Sat, 28 Oct 2017, Brian May wrote:
> I didn't realize until after I uploaded the newer version associated
> with DLA-1140-1. So I tried sending DLA-1130-1 again, followed by
> DLA-1140-1.
>
> Unfortunately DLA-1140-1 made it to the list, but DLA-1130-1 still
> didn't. I am concerned if I
Hello Guido and Moritz,
Am 30.10.2017 um 09:29 schrieb 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?
I guess we are done with the things that are
21 matches
Mail list logo
