Invalid memory access / read stack overflow when reading config with zero bytes

[Damien Miller]

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.