From: Peter Korsgaard <peter@korsgaard.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 2/2] spice: security bump to version 0.14.1
Date: Wed, 24 Oct 2018 14:24:14 +0200 [thread overview]
Message-ID: <87bm7ja5xt.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <20181017094520.4187-2-peter@korsgaard.com> (Peter Korsgaard's message of "Wed, 17 Oct 2018 11:45:19 +0200")
>>>>> "Peter" == Peter Korsgaard <peter@korsgaard.com> writes:
> Fixes CVE-2018-10873: A vulnerability was discovered in SPICE before version
> 0.14.1 where the generated code used for demarshalling messages lacked
> sufficient bounds checks. A malicious client or server, after
> authentication, could send specially crafted messages to its peer which
> would result in a crash or, potentially, other impacts.
> Drop patches as they are now upstream.
> Add host-pkgconf as the configure script uses pkg-config. Drop removed
> --disable-automated-tests configure flag.
> Add optional opus support, as that is now supported and needs to be
> explicitly disabled to not use. Explicitly disable optional gstreamer
> support for now as the dependency tree is fairly complicated.
> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
Committed to 2018.02.x and 2018.08.x, thanks.
--
Bye, Peter Korsgaard
next prev parent reply other threads:[~2018-10-24 12:24 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-17 9:45 [Buildroot] [PATCH 1/2] spice-protocol: bump version to 0.12.14 Peter Korsgaard
2018-10-17 9:45 ` [Buildroot] [PATCH 2/2] spice: security bump to version 0.14.1 Peter Korsgaard
2018-10-20 13:33 ` Peter Korsgaard
2018-10-24 12:24 ` Peter Korsgaard [this message]
2018-10-20 13:33 ` [Buildroot] [PATCH 1/2] spice-protocol: bump version to 0.12.14 Peter Korsgaard
2018-10-24 12:24 ` 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=87bm7ja5xt.fsf@dell.be.48ers.dk \
--to=peter@korsgaard.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