Hi,
On Tue, Jun 14, 2016 at 03:00:08PM +0100, James Cowgill wrote:
> On Tue, 2016-06-14 at 15:43 +0200, Petter Reinholdtsen wrote:
> > [James Cowgill]
> > > I can fix it right now in Debian (along with a few other things). Hold
> > > on a moment...
> >
> > Very good. Via the upstream github
On Tue, 2016-06-14 at 15:43 +0200, Petter Reinholdtsen wrote:
> [James Cowgill]
> > I can fix it right now in Debian (along with a few other things). Hold
> > on a moment...
>
> Very good. Via the upstream github pull request I discovered that
> Ubuntu already uploaded a fix, available as a
[James Cowgill]
> I can fix it right now in Debian (along with a few other things). Hold
> on a moment...
Very good. Via the upstream github pull request I discovered that
Ubuntu already uploaded a fix, available as a rather messy patch from
Processing control commands:
> forwarded -1 https://github.com/mpruett/audiofile/pull/25
Bug #801102 [audiofile] audiofile: CVE-2015-7747
Set Bug forwarded-to-address to 'https://github.com/mpruett/audiofile/pull/25'.
--
801102: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=801102
Debian Bug
Control: forwarded -1 https://github.com/mpruett/audiofile/pull/25
Hi,
On Mon, 2016-06-13 at 11:20 +0200, Petter Reinholdtsen wrote:
> Hi. You get this email as author of the audiofile package. Are you
> aware of the security issue reported in Debian for audiofile, see the
> CVE entry on top of
Hi. You get this email as author of the audiofile package. Are you
aware of the security issue reported in Debian for audiofile, see the
CVE entry on top of https://bugs.debian.org/src:audiofile >. Is
there a fix available? Is the same issue reported in other bug trackers
you are aware of?
