From: Adrian Bunk <bunk@stusta.de>
To: akuster808 <akuster808@gmail.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [zeus][PATCH] sqlite: fix numerous CVEs
Date: Sat, 22 Feb 2020 22:58:20 +0200 [thread overview]
Message-ID: <20200222205820.GA9628@localhost> (raw)
In-Reply-To: <b0916411-11d3-d4f2-3d37-7a020a26375d@gmail.com>
On Sat, Feb 22, 2020 at 10:34:42AM -0800, akuster808 wrote:
> Adrian,
>
> On 2/21/20 12:59 PM, Adrian Bunk wrote:
> > From: Ross Burton <ross.burton@intel.com>
> >
> > Fix the following CVEs:
> >
> > - CVE-2019-19244
> > - CVE-2019-19880
> > - CVE-2019-19923
> > - CVE-2019-19924
> > - CVE-2019-19925
> > - CVE-2019-19926
> > - CVE-2019-19959
> > - CVE-2019-20218
> >
> > Signed-off-by: Ross Burton <ross.burton@intel.com>
> > Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
> > Signed-off-by: Adrian Bunk <bunk@stusta.de>
>
> Thanks for backporting these changes. One question. The master commit
> f3ebf3f8dd0b4d144db451a8fcb352762f7fbd75
> <https://git.openembedded.org/openembedded-core/commit/meta/recipes-support/sqlite?id=f3ebf3f8dd0b4d144db451a8fcb352762f7fbd75>
> has merge conflicts
The patches are new files, so merge conflicts are impossbile on them
(they might not apply, but git does not even know that they are patches).
> and there is no mention in the commit message that
> you made any changes to get them to apply.
>
> Did you have to fixup any of the patches?
No.
> Master and Zeus have different versions of sqlite.
Yes, changing SRC_URI in the correct file was the trivial change needed.
> - armin
cu
Adrian
next prev parent reply other threads:[~2020-02-22 20:58 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-21 20:59 [zeus][PATCH] sqlite: fix numerous CVEs Adrian Bunk
2020-02-22 18:34 ` akuster808
2020-02-22 20:58 ` Adrian Bunk [this message]
2020-02-26 4:52 ` Anuj Mittal
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=20200222205820.GA9628@localhost \
--to=bunk@stusta.de \
--cc=akuster808@gmail.com \
--cc=openembedded-core@lists.openembedded.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.