Security fixes from the January 2017 CPU

Debian Bug report logs - #851233
Security fixes from the January 2017 CPU

Toggle useless messages

Message #5 received at submit@bugs.debian.org (full text, mbox, reply):

From: "Norvald H. Ryeng" <norvald.ryeng@oracle.com>

To: submit@bugs.debian.org

Subject: Security fixes from the January 2017 CPU

Date: Fri, 13 Jan 2017 09:19:19 +0100

Source: mysql-5.5
Version: 5.5.53-0+deb8u1
Severity: grave
Tags: security upstream fixed-upstream

The Oracle Critical Patch Update for January 2017 will be released on  
Tuesday, January 17. According to the pre-release announcement [1], it  
will contain information about CVEs fixed in MySQL 5.5.54.

The CVE numbers will be available when the CPU is released.

Regards,

Norvald H. Ryeng

[1] http://www.oracle.com/technetwork/security-advisory/cpujan2017-2881727.html

Message #12 received at 851233@bugs.debian.org (full text, mbox, reply):

From: Lars Tangvald <lars.tangvald@oracle.com>

To: <851233@bugs.debian.org>, <norvald.ryeng@oracle.com>

Subject: Re: [debian-mysql] Bug#851233: Security fixes from the January 2017 CPU

Date: Tue, 17 Jan 2017 12:48:38 -0800 (PST)

I've built and tested the updates, and will pass debdiffs on to the security team once the CVE list is available.

--
Lars
----- norvald.ryeng@oracle.com wrote:

> Source: mysql-5.5
> Version: 5.5.53-0+deb8u1
> Severity: grave
> Tags: security upstream fixed-upstream
> 
> The Oracle Critical Patch Update for January 2017 will be released on 
> 
> Tuesday, January 17. According to the pre-release announcement [1], it
>  
> will contain information about CVEs fixed in MySQL 5.5.54.
> 
> The CVE numbers will be available when the CPU is released.
> 
> Regards,
> 
> Norvald H. Ryeng
> 
> [1]
> http://www.oracle.com/technetwork/security-advisory/cpujan2017-2881727.html
> 
> _______________________________________________
> pkg-mysql-maint mailing list
> pkg-mysql-maint@lists.alioth.debian.org
> http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-mysql-maint

Message #17 received at 851233@bugs.debian.org (full text, mbox, reply):

From: Lars Tangvald <lars.tangvald@oracle.com>

To: "Norvald H. Ryeng" <norvald.ryeng@oracle.com>, 851233@bugs.debian.org

Subject: Re: [debian-mysql] Bug#851233: Security fixes from the January 2017 CPU

Date: Wed, 18 Jan 2017 09:21:53 +0100

CVE List for 5.5:

CVE-2017-3238
CVE-2017-3243
CVE-2017-3244
CVE-2017-3258
CVE-2017-3265
CVE-2017-3291
CVE-2017-3312
CVE-2017-3313
CVE-2017-3317
CVE-2017-3318

--
Lars
On 01/13/2017 09:19 AM, Norvald H. Ryeng wrote:
> Source: mysql-5.5
> Version: 5.5.53-0+deb8u1
> Severity: grave
> Tags: security upstream fixed-upstream
>
> The Oracle Critical Patch Update for January 2017 will be released on
> Tuesday, January 17. According to the pre-release announcement [1], it
> will contain information about CVEs fixed in MySQL 5.5.54.
>
> The CVE numbers will be available when the CPU is released.
>
> Regards,
>
> Norvald H. Ryeng
>
> [1] http://www.oracle.com/technetwork/security-advisory/cpujan2017-2881727.html
>
> _______________________________________________
> pkg-mysql-maint mailing list
> pkg-mysql-maint@lists.alioth.debian.org
> http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-mysql-maint

Message #22 received at 851233@bugs.debian.org (full text, mbox, reply):

From: Lars Tangvald <lars.tangvald@oracle.com>

To: "Norvald H. Ryeng" <norvald.ryeng@oracle.com>, 851233@bugs.debian.org, team@security.debian.org, Debian MySQL Maintainers <pkg-mysql-maint@lists.alioth.debian.org>

Subject: Re: [debian-mysql] Bug#851233: Bug#851233: Security fixes from the January 2017 CPU

Date: Wed, 18 Jan 2017 10:33:30 +0100

[Message part 1 (text/plain, inline)]

Hi,

The update builds and passes testing.
I've attached debdiff output for Wheezy and Jessie for this update. 
Aside from the changelog, the only change to packaging is a patch for a 
test (main.events_2) that was failing because of a hardcoded date.

--
Lars

[jessiedebdiff.txt.gz (application/gzip, attachment)]

[jessiedebiandiff.txt (text/plain, attachment)]

[wheezydebdiff.txt.gz (application/gzip, attachment)]

[wheezydebiandiff.txt (text/plain, attachment)]

Message #27 received at 851233@bugs.debian.org (full text, mbox, reply):

From: Salvatore Bonaccorso <carnil@debian.org>

To: Lars Tangvald <lars.tangvald@oracle.com>, 851233@bugs.debian.org

Cc: "Norvald H. Ryeng" <norvald.ryeng@oracle.com>, team@security.debian.org, Debian MySQL Maintainers <pkg-mysql-maint@lists.alioth.debian.org>

Subject: Re: [debian-mysql] Bug#851233: Bug#851233: Security fixes from the January 2017 CPU

Date: Wed, 18 Jan 2017 12:39:13 +0100

Hi Lars,

On Wed, Jan 18, 2017 at 10:33:30AM +0100, Lars Tangvald wrote:
> Hi,
> 
> The update builds and passes testing.
> I've attached debdiff output for Wheezy and Jessie for this update. Aside
> from the changelog, the only change to packaging is a patch for a test
> (main.events_2) that was failing because of a hardcoded date.

Thanks for preparing the update.

> diff -r mysql-5.5-5.5.53/debian/changelog ../mysql-5.5/mysql-5.5/debian/changelog
> 0a1,14
> > mysql-5.5 (5.5.54-0+deb8u1) jessie-security; urgency=high
> > 
> >   * Imported upstream version 5.5.54 to fix security issues:
> >     - http://www.oracle.com/technetwork/security-advisory/cpujan2017-2881727.html
> >     - CVE-2017-3238 CVE-2017-3243 CVE-2017-3244 CVE-2017-3258
> >     - CVE-2017-3265 CVE-2017-3291 CVE-2017-3312 CVE-2017-3313
> >     - CVE-2017-3317 CVE-2017-3318
> >     (Closes: #851233)
> >   * Fix failing test main.events_2
> >     The test was failing due to hardcoded date (2017-01-01). Added patch
> >     pending upstream fix.
> > 
> >  -- Lars Tangvald <lars.tangvald@oracle.com>  Tue, 17 Jan 2017 13:04:58 +0100

This looks good, but see one change which seem included below:

> 5c19
> <     - CVE-2016-7440 CVE-2016-5584
> ---
> >     - CVE-2016-6662 CVE-2016-7440 CVE-2016-5584

Did you build not on top of the last update? Because we corrected the
CVE ids in the 5.5.53-0+deb8u1 upload. CVE-2016-6662 does not belong
there, and was already fixed in the DSA-3666-1 with mysql-5.5
5.5.52-0+deb8u1, cf. the resulting changelog for 5.5.53-0+deb8u1 in
https://bugs.debian.org/841050#62 for the DSA-3666-1 upload . I don't
remember exactly, but I though I had asked someone of the mysql
packaging team to import the final changes to the packaging
repository.

With that fixed, and build with -sa (to include the orig tarball)
please do upload to security-master.

Thanks for your work!

Regards,
Salvatore

Message #32 received at 851233@bugs.debian.org (full text, mbox, reply):

From: Lars Tangvald <lars.tangvald@oracle.com>

To: Salvatore Bonaccorso <carnil@debian.org>, 851233@bugs.debian.org

Cc: "Norvald H. Ryeng" <norvald.ryeng@oracle.com>, team@security.debian.org, Debian MySQL Maintainers <pkg-mysql-maint@lists.alioth.debian.org>

Subject: Re: [debian-mysql] Bug#851233: Bug#851233: Security fixes from the January 2017 CPU

Date: Wed, 18 Jan 2017 12:45:45 +0100

Hi,

On 01/18/2017 12:39 PM, Salvatore Bonaccorso wrote:
> Hi Lars,
>
> On Wed, Jan 18, 2017 at 10:33:30AM +0100, Lars Tangvald wrote:
>> Hi,
>>
>> The update builds and passes testing.
>> I've attached debdiff output for Wheezy and Jessie for this update. Aside
>> from the changelog, the only change to packaging is a patch for a test
>> (main.events_2) that was failing because of a hardcoded date.
> Thanks for preparing the update.
>
>> diff -r mysql-5.5-5.5.53/debian/changelog ../mysql-5.5/mysql-5.5/debian/changelog
>> 0a1,14
>>> mysql-5.5 (5.5.54-0+deb8u1) jessie-security; urgency=high
>>>
>>>    * Imported upstream version 5.5.54 to fix security issues:
>>>      - http://www.oracle.com/technetwork/security-advisory/cpujan2017-2881727.html
>>>      - CVE-2017-3238 CVE-2017-3243 CVE-2017-3244 CVE-2017-3258
>>>      - CVE-2017-3265 CVE-2017-3291 CVE-2017-3312 CVE-2017-3313
>>>      - CVE-2017-3317 CVE-2017-3318
>>>      (Closes: #851233)
>>>    * Fix failing test main.events_2
>>>      The test was failing due to hardcoded date (2017-01-01). Added patch
>>>      pending upstream fix.
>>>
>>>   -- Lars Tangvald <lars.tangvald@oracle.com>  Tue, 17 Jan 2017 13:04:58 +0100
> This looks good, but see one change which seem included below:
>
>> 5c19
>> <     - CVE-2016-7440 CVE-2016-5584
>> ---
>>>      - CVE-2016-6662 CVE-2016-7440 CVE-2016-5584
> Did you build not on top of the last update? Because we corrected the
> CVE ids in the 5.5.53-0+deb8u1 upload. CVE-2016-6662 does not belong
> there, and was already fixed in the DSA-3666-1 with mysql-5.5
> 5.5.52-0+deb8u1, cf. the resulting changelog for 5.5.53-0+deb8u1 in
> https://bugs.debian.org/841050#62 for the DSA-3666-1 upload . I don't
> remember exactly, but I though I had asked someone of the mysql
> packaging team to import the final changes to the packaging
> repository.
Aha, yes. I see the vcs hasn't got the 5.5.53 packages imported 
properly. I'll do the import and rebuild, thanks.
> With that fixed, and build with -sa (to include the orig tarball)
> please do upload to security-master.
Do we have access to upload here? I think the security team have handled 
the upload in the past.

--
Lars
> Thanks for your work!
>
> Regards,
> Salvatore

Message #37 received at 851233@bugs.debian.org (full text, mbox, reply):

From: Salvatore Bonaccorso <carnil@debian.org>

To: Lars Tangvald <lars.tangvald@oracle.com>

Cc: 851233@bugs.debian.org, "Norvald H. Ryeng" <norvald.ryeng@oracle.com>, team@security.debian.org, Debian MySQL Maintainers <pkg-mysql-maint@lists.alioth.debian.org>

Subject: Re: [debian-mysql] Bug#851233: Bug#851233: Security fixes from the January 2017 CPU

Date: Wed, 18 Jan 2017 14:38:30 +0100

Hi Lars,

On Wed, Jan 18, 2017 at 12:45:45PM +0100, Lars Tangvald wrote:
> Hi,
> 
> On 01/18/2017 12:39 PM, Salvatore Bonaccorso wrote:
> >Hi Lars,
> >
> >On Wed, Jan 18, 2017 at 10:33:30AM +0100, Lars Tangvald wrote:
> >>Hi,
> >>
> >>The update builds and passes testing.
> >>I've attached debdiff output for Wheezy and Jessie for this update. Aside
> >>from the changelog, the only change to packaging is a patch for a test
> >>(main.events_2) that was failing because of a hardcoded date.
> >Thanks for preparing the update.
> >
> >>diff -r mysql-5.5-5.5.53/debian/changelog ../mysql-5.5/mysql-5.5/debian/changelog
> >>0a1,14
> >>>mysql-5.5 (5.5.54-0+deb8u1) jessie-security; urgency=high
> >>>
> >>>   * Imported upstream version 5.5.54 to fix security issues:
> >>>     - http://www.oracle.com/technetwork/security-advisory/cpujan2017-2881727.html
> >>>     - CVE-2017-3238 CVE-2017-3243 CVE-2017-3244 CVE-2017-3258
> >>>     - CVE-2017-3265 CVE-2017-3291 CVE-2017-3312 CVE-2017-3313
> >>>     - CVE-2017-3317 CVE-2017-3318
> >>>     (Closes: #851233)
> >>>   * Fix failing test main.events_2
> >>>     The test was failing due to hardcoded date (2017-01-01). Added patch
> >>>     pending upstream fix.
> >>>
> >>>  -- Lars Tangvald <lars.tangvald@oracle.com>  Tue, 17 Jan 2017 13:04:58 +0100
> >This looks good, but see one change which seem included below:
> >
> >>5c19
> >><     - CVE-2016-7440 CVE-2016-5584
> >>---
> >>>     - CVE-2016-6662 CVE-2016-7440 CVE-2016-5584
> >Did you build not on top of the last update? Because we corrected the
> >CVE ids in the 5.5.53-0+deb8u1 upload. CVE-2016-6662 does not belong
> >there, and was already fixed in the DSA-3666-1 with mysql-5.5
> >5.5.52-0+deb8u1, cf. the resulting changelog for 5.5.53-0+deb8u1 in
> >https://bugs.debian.org/841050#62 for the DSA-3666-1 upload . I don't
> >remember exactly, but I though I had asked someone of the mysql
> >packaging team to import the final changes to the packaging
> >repository.
> Aha, yes. I see the vcs hasn't got the 5.5.53 packages imported properly.
> I'll do the import and rebuild, thanks.

Thanks!

> >With that fixed, and build with -sa (to include the orig tarball)
> >please do upload to security-master.
> Do we have access to upload here? I think the security team have handled the
> upload in the past.

yes it nees to be a key in the DD keyring. Do you have a DD in the
mysql-pkg team who could sponsor the upload?

Regards,
Salvatore

Message #42 received at 851233@bugs.debian.org (full text, mbox, reply):

From: Lars Tangvald <lars.tangvald@oracle.com>

To: <carnil@debian.org>

Cc: <team@security.debian.org>, <851233@bugs.debian.org>, <pkg-mysql-maint@lists.alioth.debian.org>, <norvald.ryeng@oracle.com>

Subject: Re: [debian-mysql] Bug#851233: Bug#851233: Security fixes from the January 2017 CPU

Date: Wed, 18 Jan 2017 06:41:40 -0800 (PST)

----- carnil@debian.org wrote:


> > >With that fixed, and build with -sa (to include the orig tarball)
> > >please do upload to security-master.
> > Do we have access to upload here? I think the security team have
> handled the
> > upload in the past.
> 
> yes it nees to be a key in the DD keyring. Do you have a DD in the
> mysql-pkg team who could sponsor the upload?
> 

Not really, unfortunately (Otto is a DD, but he's only involved with the MariaDB packaging).
It's an issue for us, since it also causes problems with uploads to unstable.

--
Lars

Message #47 received at 851233@bugs.debian.org (full text, mbox, reply):

From: Salvatore Bonaccorso <carnil@debian.org>

To: Lars Tangvald <lars.tangvald@oracle.com>

Cc: team@security.debian.org, 851233@bugs.debian.org, pkg-mysql-maint@lists.alioth.debian.org, norvald.ryeng@oracle.com

Subject: Re: [debian-mysql] Bug#851233: Bug#851233: Security fixes from the January 2017 CPU

Date: Wed, 18 Jan 2017 16:26:58 +0100

Hi Lars,

On Wed, Jan 18, 2017 at 06:41:40AM -0800, Lars Tangvald wrote:
> 
> ----- carnil@debian.org wrote:
> 
> 
> > > >With that fixed, and build with -sa (to include the orig tarball)
> > > >please do upload to security-master.
> > > Do we have access to upload here? I think the security team have
> > handled the
> > > upload in the past.
> > 
> > yes it nees to be a key in the DD keyring. Do you have a DD in the
> > mysql-pkg team who could sponsor the upload?
> > 
> 
> Not really, unfortunately (Otto is a DD, but he's only involved with
> the MariaDB packaging).
> It's an issue for us, since it also causes problems with uploads to
> unstable.

Ok. I though in the past James Page was sponsoring the uploads.
Alright, in that case, let me know when you have finished the
packaging with the small changes mentioned, I can take care of
sponsoring the upload.

Regards,
Salvatore

Message #52 received at 851233@bugs.debian.org (full text, mbox, reply):

From: Lars Tangvald <lars.tangvald@oracle.com>

To: <carnil@debian.org>

Cc: <team@security.debian.org>, <851233@bugs.debian.org>, <pkg-mysql-maint@lists.alioth.debian.org>, <norvald.ryeng@oracle.com>

Subject: Re: [debian-mysql] Bug#851233: Bug#851233: Security fixes from the January 2017 CPU

Date: Wed, 18 Jan 2017 07:57:50 -0800 (PST)

----- carnil@debian.org wrote:

> Hi Lars,
> 
> On Wed, Jan 18, 2017 at 06:41:40AM -0800, Lars Tangvald wrote:
> > 
> > ----- carnil@debian.org wrote:
> > 
> > 
> > > > >With that fixed, and build with -sa (to include the orig
> tarball)
> > > > >please do upload to security-master.
> > > > Do we have access to upload here? I think the security team
> have
> > > handled the
> > > > upload in the past.
> > > 
> > > yes it nees to be a key in the DD keyring. Do you have a DD in
> the
> > > mysql-pkg team who could sponsor the upload?
> > > 
> > 
> > Not really, unfortunately (Otto is a DD, but he's only involved
> with
> > the MariaDB packaging).
> > It's an issue for us, since it also causes problems with uploads to
> > unstable.
> 
> Ok. I though in the past James Page was sponsoring the uploads.
> Alright, in that case, let me know when you have finished the
> packaging with the small changes mentioned, I can take care of
> sponsoring the upload.
> 
I might be going a bit senile, since I forgot he's got access as well, but for the last months he's been occupied, so I don't think he's available now.
I'll let you know when the new build is ready, thanks.

--
Lars
> Regards,
> Salvatore

Message #57 received at 851233@bugs.debian.org (full text, mbox, reply):

From: Lars Tangvald <lars.tangvald@oracle.com>

To: <carnil@debian.org>

Cc: <team@security.debian.org>, <851233@bugs.debian.org>, <pkg-mysql-maint@lists.alioth.debian.org>, <norvald.ryeng@oracle.com>

Subject: Re: [debian-mysql] Bug#851233: Bug#851233: Security fixes from the January 2017 CPU

Date: Wed, 18 Jan 2017 11:23:17 -0800 (PST)

[Message part 1 (text/plain, inline)]

----- carnil@debian.org wrote:
[...]
> 
> Ok. I though in the past James Page was sponsoring the uploads.
> Alright, in that case, let me know when you have finished the
> packaging with the small changes mentioned, I can take care of
> sponsoring the upload.
> 
> Regards,
> Salvatore

Attaching new versions with the changelogs fixed (wheezy build was also missing a changelog entry from the LTS team)

--
Lars

[jessiedebdiff.txt.gz (application/gzip, attachment)]

[jessiedebiandiff.txt (text/plain, attachment)]

[wheezydebdiff.txt.gz (application/gzip, attachment)]

[wheezydebiandiff.txt (text/plain, attachment)]

Message #62 received at 851233-close@bugs.debian.org (full text, mbox, reply):

From: Lars Tangvald <lars.tangvald@oracle.com>

To: 851233-close@bugs.debian.org

Subject: Bug#851233: fixed in mysql-5.5 5.5.54-0+deb8u1

Date: Sat, 28 Jan 2017 12:32:28 +0000

Source: mysql-5.5
Source-Version: 5.5.54-0+deb8u1

We believe that the bug you reported is fixed in the latest version of
mysql-5.5, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 851233@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Lars Tangvald <lars.tangvald@oracle.com> (supplier of updated mysql-5.5 package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmaster@ftp-master.debian.org)


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

Format: 1.8
Date: Tue, 17 Jan 2017 13:04:58 +0100
Source: mysql-5.5
Binary: libmysqlclient18 libmysqld-pic libmysqld-dev libmysqlclient-dev mysql-common mysql-client-5.5 mysql-server-core-5.5 mysql-server-5.5 mysql-server mysql-client mysql-testsuite mysql-testsuite-5.5 mysql-source-5.5
Architecture: all source
Version: 5.5.54-0+deb8u1
Distribution: jessie-security
Urgency: high
Maintainer: Debian MySQL Maintainers <pkg-mysql-maint@lists.alioth.debian.org>
Changed-By: Lars Tangvald <lars.tangvald@oracle.com>
Closes: 851233
Description: 
 libmysqlclient-dev - MySQL database development files
 libmysqlclient18 - MySQL database client library
 libmysqld-dev - MySQL embedded database development files
 libmysqld-pic - PIC version of MySQL embedded server development files
 mysql-client - MySQL database client (metapackage depending on the latest versio
 mysql-client-5.5 - MySQL database client binaries
 mysql-common - MySQL database common files, e.g. /etc/mysql/my.cnf
 mysql-server - MySQL database server (metapackage depending on the latest versio
 mysql-server-5.5 - MySQL database server binaries and system database setup
 mysql-server-core-5.5 - MySQL database server binaries
 mysql-source-5.5 - MySQL source
 mysql-testsuite - MySQL testsuite
 mysql-testsuite-5.5 - MySQL testsuite
Changes:
 mysql-5.5 (5.5.54-0+deb8u1) jessie-security; urgency=high
 .
   * Imported upstream version 5.5.54 to fix security issues:
     - http://www.oracle.com/technetwork/security-advisory/cpujan2017-2881727.html
     - CVE-2017-3238 CVE-2017-3243 CVE-2017-3244 CVE-2017-3258
     - CVE-2017-3265 CVE-2017-3291 CVE-2017-3312 CVE-2017-3313
     - CVE-2017-3317 CVE-2017-3318
     (Closes: #851233)
   * Fix failing test main.events_2
     The test was failing due to hardcoded date (2017-01-01). Added patch
     pending upstream fix.
Checksums-Sha1: 
 ccbe9a7d1ac37b643204e92f19725979375ecd87 3262 mysql-5.5_5.5.54-0+deb8u1.dsc
 a1089abcd5d4b8d34d5bbc5c13acb8919bc63ba0 21041949 mysql-5.5_5.5.54.orig.tar.gz
 9435272031315cf354c518af3cdaae239b5ab309 233108 mysql-5.5_5.5.54-0+deb8u1.debian.tar.xz
 ccffe39684c6478524a8412bdc384f1da74a2737 81150 mysql-common_5.5.54-0+deb8u1_all.deb
 61cd4e1357fd2f45f4ca79f124aaee26f3171ec0 79462 mysql-server_5.5.54-0+deb8u1_all.deb
 883c2445591c5cc6bab1b0f30d748f44ef92504b 79332 mysql-client_5.5.54-0+deb8u1_all.deb
 35e97f00be34738334b8daf9ed4628ff911e921c 79300 mysql-testsuite_5.5.54-0+deb8u1_all.deb
Checksums-Sha256: 
 993b22375e92261e9ab264b5cd380d439dfd61524680c3edf301150caf416712 3262 mysql-5.5_5.5.54-0+deb8u1.dsc
 273bcbcf8cc84061eb07c359308563b2029eb3f70f78b558905bc1b5c5791ab8 21041949 mysql-5.5_5.5.54.orig.tar.gz
 946211b6bac4d0a20911e8a8c01bf30d48fe875fb8987eea2147ec9b21eba896 233108 mysql-5.5_5.5.54-0+deb8u1.debian.tar.xz
 82378b931ed58d7d377af3f9c289e32dba386dc94e8881a63a76694a07a92cd1 81150 mysql-common_5.5.54-0+deb8u1_all.deb
 18ab743c840260244b2cfd3ae45e89366293c23d5a7346a4ae9d1505688af236 79462 mysql-server_5.5.54-0+deb8u1_all.deb
 7152753c0539e6eed291332b802cbf503920528580778cac7671d72b384d848a 79332 mysql-client_5.5.54-0+deb8u1_all.deb
 bc13c9f494a6216e6db1a02ce6f877ef08793d0d7053feded9f3abc6efe03d7b 79300 mysql-testsuite_5.5.54-0+deb8u1_all.deb
Files: 
 3fbf82935d6b8e4c3227c675eef53683 3262 database optional mysql-5.5_5.5.54-0+deb8u1.dsc
 358b596e62699397aeee3dfb469f5823 21041949 database optional mysql-5.5_5.5.54.orig.tar.gz
 1f63718e096acf26ce7401ad23828b2e 233108 database optional mysql-5.5_5.5.54-0+deb8u1.debian.tar.xz
 3ae5e9f5982430d13628526a617a384c 81150 database optional mysql-common_5.5.54-0+deb8u1_all.deb
 a08a6b01b6c3be701ca3c2f67a077988 79462 database optional mysql-server_5.5.54-0+deb8u1_all.deb
 a6031a274e8068d3dee728914f1bd3fc 79332 database optional mysql-client_5.5.54-0+deb8u1_all.deb
 d39893d0c84b0cd664061672f0c56832 79300 database optional mysql-testsuite_5.5.54-0+deb8u1_all.deb

-----BEGIN PGP SIGNATURE-----

iQKmBAEBCgCQFiEERkRAmAjBceBVMd3uBUy48xNDz0QFAliAebhfFIAAAAAALgAo
aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldDQ2
NDQ0MDk4MDhDMTcxRTA1NTMxRERFRTA1NENCOEYzMTM0M0NGNDQSHGNhcm5pbEBk
ZWJpYW4ub3JnAAoJEAVMuPMTQ89EDrgP/jD1q7NZS8SV1Ef9dWh5h7p7nMTPFAE2
Ti8jLBMQwEHm8Ya0zrt4mrZfz4GN0X/nDqadtV3EgE/XJCVWaNdA83rlnOoOb1rY
P3ViXr8/8XJ0twC4jEJZ4iWIgY3iD8OsH18aF/MIPwLd7hKpLjzn7h/UZY8Q3Ia1
Xi0iXl0j9ZBtWKd1pE1B1i9f40CXTNMI6YNsTI/K4EppUGfqPiaYkHCiiQVHUjX8
uwBBSOJq2exBW6rWDioGI5/hYZJ93AeSe3CjIWblVp/bAISKtILyqQmgLTbpWWg2
FF+Mnuq624GO/lZobFX1UiWU2NWZ9CZ2fC34QDuDyuDFfW8qI0PPc+n0lF2rF22p
k2CEwR43CrX9jcrnbVY1mnEg1Ulie+OoDeX5s53vt7DnEcaKEvmCgka3yigbI24N
2XsfCW9JJM4sg5jyOGGSLI3b1P8j0StWY/tbI2lUasFkYJd28XjfGApl4LYqHilZ
7bxLdmZeBBByEt5NyjD84ZUB3E7FgF7CkLtxQ/dCeGETy7EPkpeSJu3T7/61LOeG
38iv4O7Fp+6p1jjs/ezjd7Qg2QLn7Qs4cWUl7knAtP96hf0QcwXLxpjirMivHva6
0sbr9xvysZAZv8h4O7/iSRNG4pFr2fb4hk4uBrIYI6E+9P7ND64Obvt4AXz0YWvD
AEazEBLz9J7J
=Wx+X
-----END PGP SIGNATURE-----

Send a report that this bug log contains spam.