From: Leo Famulari <leo@famulari.name>
To: Alex Vong <alexvong1995@gmail.com>
Cc: 30378@debbugs.gnu.org
Subject: [bug#30378] [PATCH] gnu: mpv: Fix CVE-2018-6360.
Date: Thu, 8 Feb 2018 14:16:06 -0500 [thread overview]
Message-ID: <20180208191606.GA21732@jasmine.lan> (raw)
In-Reply-To: <87mv0kqb67.fsf@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 871 bytes --]
On Thu, Feb 08, 2018 at 01:53:52PM +0800, Alex Vong wrote:
> Leo Famulari <leo@famulari.name> writes:
> > I noticed that the person who fixed the bug upstream said that 4 commits
> > were needed [0], but this patch (and Debian's and Nix's) are missing the
> > first in that person's list, 828bd2963cd10.
> >
> > I'm going to ask upstream to clarify but, in the meantime, do you know
> > why this patch is not included?
> >
> I have no idea about this. I think we should wait for the author to tell
> us what they think. Here is a new patch with the 4 commits:
Upstream clarified that the "missing" commit is not actually necessary
here:
"Yeah, nevermind. Being able to use the native dash demuxer is not
necessary for the security fixes."
https://github.com/mpv-player/mpv/issues/5456#issuecomment-364087205
So I'm going to test and push your original patch shortly.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2018-02-08 19:17 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-07 6:53 [bug#30378] [PATCH] gnu: mpv: Fix CVE-2018-6360 Alex Vong
2018-02-07 6:59 ` Alex Vong
2018-02-08 2:44 ` Leo Famulari
2018-02-08 5:53 ` Alex Vong
2018-02-08 19:16 ` Leo Famulari [this message]
2018-02-08 20:19 ` bug#30378: " Leo Famulari
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20180208191606.GA21732@jasmine.lan \
--to=leo@famulari.name \
--cc=30378@debbugs.gnu.org \
--cc=alexvong1995@gmail.com \
/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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).