From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] package/vlc: security bump version to 3.0.12
Date: Fri, 22 Jan 2021 13:54:42 +0100 [thread overview]
Message-ID: <20210122135442.7bb32ec1@windsurf.home> (raw)
In-Reply-To: <87y2gl8ivg.fsf@dell.be.48ers.dk>
On Fri, 22 Jan 2021 09:40:19 +0100
Peter Korsgaard <peter@korsgaard.com> wrote:
> >>>>> "Bernd" == Bernd Kuhls <bernd.kuhls@t-online.de> writes:
>
> > Removed patch which was applied upstream, removed md5 hash.
> > Security Bulletin: https://www.videolan.org/security/sb-vlc3012.html
> > Fixes CVE-2020-26664: https://nvd.nist.gov/vuln/detail/CVE-2020-26664
>
> > Added CPE_ID, cpe:2.3:a:videolan:vlc_media_player is a valid CPE
> > identifier for this package:
> > https://nvd.nist.gov/products/cpe/search/results?namingFormat=2.3&orderBy=2.3&keyword=cpe%3A2.3%3Aa%3Avideolan%3Avlc_media_player&status=FINAL
>
> > Signed-off-by: Bernd Kuhls <bernd.kuhls@t-online.de>
>
> Committed to 2020.02.x and 2020.11.x, thanks.
Regarding the backport to 2020.02.x/2020.11.x, I almost asked Bernd to
change the patch to split the version bump from the CPE information
addition. Indeed, the CPE information added by this patch doesn't make
much sense in the context of 2020.02.x.
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2021-01-22 12:54 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-20 7:39 [Buildroot] [PATCH 1/1] package/vlc: security bump version to 3.0.12 Bernd Kuhls
2021-01-21 21:41 ` Thomas Petazzoni
2021-01-22 8:40 ` Peter Korsgaard
2021-01-22 12:54 ` Thomas Petazzoni [this message]
2021-01-22 15:30 ` 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=20210122135442.7bb32ec1@windsurf.home \
--to=thomas.petazzoni@bootlin.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