From: Ryan Coe <bluemrp9@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] mariadb: security bump to version 10.1.23
Date: Fri, 12 May 2017 06:44:50 -0700 [thread overview]
Message-ID: <7f264a9b-c5cf-feaf-a8bf-929d112fb7f0@gmail.com> (raw)
In-Reply-To: <87efvzno6c.fsf@dell.be.48ers.dk>
Peter, All,
On 5/8/2017 12:28 PM, Peter Korsgaard wrote:
>>>>>> "Ryan" == Ryan Coe <bluemrp9@gmail.com> writes:
> > Fixes:
> > CVE-2017-3302 - Crash in libmysqlclient.so in Oracle MySQL before 5.6.21 and
> > 5.7.x before 5.7.5 and MariaDB through 5.5.54, 10.0.x through 10.0.29,
> > 10.1.x through 10.1.21, and 10.2.x through 10.2.3.
>
> [snip]
>
> > -MARIADB_VERSION = 10.1.22
> > +MARIADB_VERSION = 10.1.23
> > MARIADB_SITE = https://downloads.mariadb.org/interstitial/mariadb-$(MARIADB_VERSION)/source
> > MARIADB_LICENSE = GPL-2.0 (server), GPL-2.0 with FLOSS exception (GPL
> > client library), LGPL-2.0 (LGPL client library)
> > MARIADB_LICENSE_FILES = README COPYING COPYING.LESSER
>
> Thanks, I (obviously) want to apply this, but something odd is going on
> with the licensing. COPYING.LESSER has been removed by this commit:
>
> https://github.com/MariaDB/server/commit/577915def8
>
> But the client library IS listed as being LGPL:
>
> https://mariadb.com/kb/en/mariadb/mariadb-connector-c/
>
> And same for the "old" one:
>
> https://mariadb.com/kb/en/mariadb/lgpl-mysql-client-library-32358/
>
> Grepping around in the 10.1.23 tarball, I don't see a lot of references
> to Lesser og LGPL.
>
> Now, I know next to nothing about mariadb. Do you have any idea what is
> going on here?
>
I am really not sure what is going on there.
next prev parent reply other threads:[~2017-05-12 13:44 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-08 15:37 [Buildroot] [PATCH 1/1] mariadb: security bump to version 10.1.23 Ryan Coe
2017-05-08 19:28 ` Peter Korsgaard
2017-05-12 13:44 ` Ryan Coe [this message]
2017-05-15 13:51 ` Peter Korsgaard
2017-05-19 15:44 ` Ryan Coe
2017-05-21 21:57 ` Peter Korsgaard
2017-06-01 14:06 ` Peter Korsgaard
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=7f264a9b-c5cf-feaf-a8bf-929d112fb7f0@gmail.com \
--to=bluemrp9@gmail.com \
--cc=buildroot@busybox.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox