sox-devel@lists.sourceforge.net unofficial mirror
 help / color / mirror / code / Atom feed
From: "Jaromír Mikeš" <mira.mikes@gmail.com>
To: Salvatore Bonaccorso <carnil@debian.org>
Cc: 878809@bugs.debian.org, sox-devel@lists.sourceforge.net
Subject: Re: Bug#878809 closed by Jaromír Mikeš <mira.mikes@seznam.cz> (Bug#878809: fixyا\xB2\x8Cu
Date: Sun, 19 Nov 2017 22:23:01 +0100	[thread overview]
Message-ID: <CAG_ZyaCo6Cu90qBfcWiXx9HtzEv48-OrT6QoO_fQXOb5R1Srow@mail.gmail.com> (raw)
In-Reply-To: <20171119201148.dlso3wp5vdk6hm2d@eldamar.local>


[-- Attachment #1.1: Type: text/plain, Size: 925 bytes --]

2017-11-19 21:11 GMT+01:00 Salvatore Bonaccorso <carnil@debian.org>:

> Control: reopen -1
> Control: found -1 14.4.1-5
> Control: found -1 14.4.2-1
> Control: tags -1 + moreinfo
>
> Hi Jaromir,
>
> Are you sure #878809 is yet fixed?
>
> With the patches applied on top of 14.4.2 we see still that sox aborts
> with:
>
> $ ./sox-14.4.2/src/sox 03-abort out.wav
> sox: formats.c:227: sox_append_comment: Assertion `comment' failed.
> Aborted
>
> So the assertion is still reachable, so at least
> 0005-CVE-2017-15371.patch did not solve the problem?
>
> What am I missing here? Note, I'm just reopening the bug as
> safetymeasure to double-check. If I turn to be wrong (likely) we can
> reclose it, but I wanted to be sure.
>

​Hi Salvatore,

can you provide some more details please. Upstream developers claims that
issue should be solved
by 0005-CVE-2017-15371.patch

best regards

mira

[-- Attachment #1.2: Type: text/html, Size: 1818 bytes --]

[-- Attachment #2: Type: text/plain, Size: 202 bytes --]

------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot

[-- Attachment #3: Type: text/plain, Size: 158 bytes --]

_______________________________________________
SoX-devel mailing list
SoX-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/sox-devel

           reply	other threads:[~2017-11-19 21:23 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <20171119201148.dlso3wp5vdk6hm2d@eldamar.local>]

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-list from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://lists.sourceforge.net/lists/listinfo/sox-devel

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CAG_ZyaCo6Cu90qBfcWiXx9HtzEv48-OrT6QoO_fQXOb5R1Srow@mail.gmail.com \
    --to=sox-devel@lists.sourceforge.net \
    --cc=878809@bugs.debian.org \
    --cc=carnil@debian.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.
Code repositories for project(s) associated with this public inbox

	https://80x24.org/mirrors/sox.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).