[debbugs-tracker] bug#27429: closed (Stack clash (CVE-2017-1000366 etc))

[GNU bug Tracking System]

Your message dated Thu, 20 Jul 2017 15:13:24 -0400
with message-id <address@hidden>
and subject line Re: bug#27429: Stack clash (CVE-2017-1000366 etc)
has caused the debbugs.gnu.org bug report #27429,
regarding Stack clash (CVE-2017-1000366 etc)
to be marked as done.

(If you believe you have received this mail in error, please contact
address@hidden)


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

--- Begin Message --- Subject: Stack clash (CVE-2017-1000366 etc) Date: Mon, 19 Jun 2017 18:25:50 -0400 User-agent: Mutt/1.8.3 (2017-05-23)

This is a place to discuss the "stack crash" bugs as they apply to our
packages.

https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-1000366
https://www.qualys.com/2017/06/19/stack-clash/stack-clash.txt

signature.asc
Description: PGP signature

--- End Message ---

--- Begin Message --- Subject: Re: bug#27429: Stack clash (CVE-2017-1000366 etc) Date: Thu, 20 Jul 2017 15:13:24 -0400 User-agent: Mutt/1.8.3 (2017-05-23)

On Thu, Jul 20, 2017 at 05:54:06PM +0200, Ludovic Courtès wrote:
> Leo Famulari <address@hidden> skribis:
> 
> > This is a place to discuss the "stack crash" bugs as they apply to our
> > packages.
> >
> > https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-1000366
> > https://www.qualys.com/2017/06/19/stack-clash/stack-clash.txt
> 
> I think we can close this bug now, can’t we?

Yeah, I'm closing it.

I think the various mitigations we applied will change and improve over
time, but they can be discussed elsewhere once we know what they are.

signature.asc
Description: PGP signature

--- End Message ---