GNU bug report logs - #26828
Update libetpan to 1.8 (CVE-2017-8825)

Previous Next

Full log

View this message in rfc822 format

From: help-debbugs <at> gnu.org (GNU bug Tracking System)
To: Leo Famulari <leo <at> famulari.name>
Cc: tracker <at> debbugs.gnu.org
Subject: bug#26828: closed (Update libetpan to 1.8 (CVE-2017-8825))
Date: Tue, 09 May 2017 17:27:01 +0000

[Message part 1 (text/plain, inline)]

Your message dated Tue, 9 May 2017 13:26:07 -0400
with message-id <20170509172607.GA8773 <at> jasmine>
and subject line Re: bug#26828: Update libetpan to 1.8 (CVE-2017-8825)
has caused the debbugs.gnu.org bug report #26828,
regarding Update libetpan to 1.8 (CVE-2017-8825)
to be marked as done.

(If you believe you have received this mail in error, please contact
help-debbugs <at> gnu.org.)


-- 
26828: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=26828
GNU Bug Tracking System
Contact help-debbugs <at> gnu.org with problems

[Message part 2 (message/rfc822, inline)]

From: Julien Lepiller <julien <at> lepiller.eu>
To: guix-patches <at> gnu.org
Subject: Update libetpan to 1.8 (CVE-2017-8825)
Date: Mon, 8 May 2017 16:43:13 +0200

[Message part 3 (text/plain, inline)]

Hi,

here is a patch to update libetpan to version 1.8. This update also
fixes CVE-2017-8825. Should it be mentionned in the commit log?

[0001-gnu-libetpan-Update-to-1.8.patch (text/x-patch, attachment)]

[Message part 5 (message/rfc822, inline)]

From: Leo Famulari <leo <at> famulari.name>
To: Julien Lepiller <julien <at> lepiller.eu>
Cc: 26828-done <at> debbugs.gnu.org
Subject: Re: bug#26828: Update libetpan to 1.8 (CVE-2017-8825)
Date: Tue, 9 May 2017 13:26:07 -0400

[Message part 6 (text/plain, inline)]

On Mon, May 08, 2017 at 01:35:38PM -0400, Leo Famulari wrote:
> On Mon, May 08, 2017 at 04:43:13PM +0200, Julien Lepiller wrote:
> > Hi,
> > 
> > here is a patch to update libetpan to version 1.8. This update also
> > fixes CVE-2017-8825. Should it be mentionned in the commit log?
> 
> Thanks! Yes, I would add [fixes CVE-2017-8825] to the end of the first
> line of the commit message.
> 
> I bet the majority of updates include fixes for exploitable bugs (at
> least for C programs), but it's still useful to include these bug
> identifiers in the commit log, when we know about them.

Hi Julien,

I pushed the patch on your behalf as
a979eea9c2132d35cba30e7fcd4184ec159310a6.

[signature.asc (application/pgp-signature, inline)]

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.