Date: Thu, 1 May 2014 13:19:54 +0100 From: Bob Bishop <rb@gid.co.uk> To: Kevin Day <toasty@dragondata.com> Cc: freebsd-security@freebsd.org Subject: Re: FreeBSD Security Advisory FreeBSD-SA-14:08.tcp Message-ID: <9C9E416B-501C-49CD-A698-93CA7848CD1D@gid.co.uk>
next in thread | raw e-mail | index | archive | help
Hi, > From: Kevin Day <toasty@dragondata.com> > To: freebsd-security@freebsd.org > Subject: Re: FreeBSD Security Advisory FreeBSD-SA-14:08.tcp >=20 > > Affects: All supported versions of FreeBSD. > > Corrected: 2014-04-30 04:04:20 UTC (stable/8, 8.4-STABLE) > > 2014-04-30 04:05:47 UTC (releng/8.4, 8.4-RELEASE-p9) > > 2014-04-30 04:05:47 UTC (releng/8.3, = 8.3-RELEASE-p16) > > 2014-04-30 04:04:20 UTC (stable/9, 9.2-STABLE) > > 2014-04-30 04:05:47 UTC (releng/9.2, 9.2-RELEASE-p5) > > 2014-04-30 04:05:47 UTC (releng/9.1, = 9.1-RELEASE-p12) > > 2014-04-30 04:03:05 UTC (stable/10, 10.0-STABLE) > > 2014-04-30 04:04:42 UTC (releng/10.0, = 10.0-RELEASE-p2) >=20 > Does anyone know the lower bound for how far back this bug exists? Is = it only present in the above versions, or does it affect earlier = versions that aren?t listed? >=20 > (trying to come up with a deployment plan for some servers stuck on = 8.1 and 7.x due to vendors abandoning device drivers) Just looked at this, 8.1 and 7.x don't have the optimisation using the = stack so they are unaffected. -- Bob Bishop rb@gid.co.uk
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?9C9E416B-501C-49CD-A698-93CA7848CD1D>