[debbugs-tracker] bug#26828: closed (Update libetpan to 1.8 (CVE-2017-8825))

[GNU bug Tracking System]

Your message dated Tue, 9 May 2017 13:26:07 -0400
with message-id <address@hidden>
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
address@hidden)


-- 
26828: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=26828
GNU Bug Tracking System
Contact address@hidden with problems

--- Begin Message --- Subject: Update libetpan to 1.8 (CVE-2017-8825) Date: Mon, 8 May 2017 16:43:13 +0200

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
Description: Text Data

--- End Message ---

--- Begin Message --- Subject: Re: bug#26828: Update libetpan to 1.8 (CVE-2017-8825) Date: Tue, 9 May 2017 13:26:07 -0400 User-agent: Mutt/1.8.2 (2017-04-18)

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
Description: PGP signature

--- End Message ---