Damien Miller
2015-Mar-29 23:34 UTC
Invalid memory access / read stack overflow when reading config with zero bytes
On Sun, 29 Mar 2015, Nico Kadel-Garcia wrote:> On Sun, Mar 29, 2015 at 6:36 PM, Hanno B?ck <hanno at hboeck.de> wrote: > > On Mon, 30 Mar 2015 09:19:02 +1100 (AEDT) > > Damien Miller <djm at mindrot.org> wrote: > > > >> What version of OpenSSH is this? > > > > 6.8 portable on Linux. > > There are a *lot* of Linux flavors. Which one?That doesn't matter much if he's using pristine sources. -d
Nico Kadel-Garcia
2015-Mar-29 23:47 UTC
Invalid memory access / read stack overflow when reading config with zero bytes
On Sun, Mar 29, 2015 at 7:34 PM, Damien Miller <djm at mindrot.org> wrote:> On Sun, 29 Mar 2015, Nico Kadel-Garcia wrote: > >> On Sun, Mar 29, 2015 at 6:36 PM, Hanno B?ck <hanno at hboeck.de> wrote: >> > On Mon, 30 Mar 2015 09:19:02 +1100 (AEDT) >> > Damien Miller <djm at mindrot.org> wrote: >> > >> >> What version of OpenSSH is this? >> > >> > 6.8 portable on Linux. >> >> There are a *lot* of Linux flavors. Which one? > > That doesn't matter much if he's using pristine sources. > > -dDiferent compiler, different glibc, different kernel, different enabled compile time options, different configuration of SELinux can all provide fascinating distinctions in behavior of the most "pristine" of software. So it's a reasonable question.
Damien Miller
2015-Mar-29 23:57 UTC
Invalid memory access / read stack overflow when reading config with zero bytes
On Sun, 29 Mar 2015, Nico Kadel-Garcia wrote:> Diferent compiler, different glibc, different kernel, different > enabled compile time options, different configuration of SELinux can > all provide fascinating distinctions in behavior of the most > "pristine" of software. So it's a reasonable question.In this case it doesn't matter; none of these affect config parsing which is where the bug was.