From: Peter Seiderer <ps.report@gmx.net>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v1 2/2] package/qt5base: add patches to fix CVE-2020-0569 and CVE-2020-0570 for latest
Date: Sun, 2 Feb 2020 09:48:35 +0100 [thread overview]
Message-ID: <20200202094835.0613f372@gmx.net> (raw)
In-Reply-To: <87sgjuorlh.fsf@dell.be.48ers.dk>
Hello Peter,
On Sat, 01 Feb 2020 23:44:26 +0100, Peter Korsgaard <peter@korsgaard.com> wrote:
> >>>>> "Peter" == Peter Seiderer <ps.report@gmx.net> writes:
>
> > Add upstream patches to fix CVE-2020-0569 and CVE-2020-0570 for
> > latest qt version (for details see [1]).
>
> > [1] https://www.openwall.com/lists/oss-security/2020/01/30/1
>
> > Signed-off-by: Peter Seiderer <ps.report@gmx.net>
>
> Committed after extending the commit message a bit, thanks.
>
> I see from the advisory that there is a 5.12.7 version with this fix
> included. Any specific reason why we don't bump the version instead?
Because the advisory states 'fixed 5.12.7 (future)'...
>
> https://download.qt.io/archive/qt/5.12/5.12.7/
>
...and the version is only available since two days (and the sha256 sums only since
yesterday)..., but version bump patch will follow soon ;-)
Regards,
Peter
next prev parent reply other threads:[~2020-02-02 8:48 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-30 21:13 [Buildroot] [PATCH v1 1/2] package/qt5base: add patch to fix CVE-2020-0569 for LTS Peter Seiderer
2020-01-30 21:13 ` [Buildroot] [PATCH v1 2/2] package/qt5base: add patches to fix CVE-2020-0569 and CVE-2020-0570 for latest Peter Seiderer
2020-02-01 22:44 ` Peter Korsgaard
2020-02-02 8:48 ` Peter Seiderer [this message]
2020-02-02 13:27 ` Peter Korsgaard
2020-03-07 20:17 ` Peter Korsgaard
2020-02-01 22:43 ` [Buildroot] [PATCH v1 1/2] package/qt5base: add patch to fix CVE-2020-0569 for LTS Peter Korsgaard
2020-03-07 20:17 ` 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=20200202094835.0613f372@gmx.net \
--to=ps.report@gmx.net \
--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