Re: [PATCH libXau] Avoid out of boundary read access

2017-10-20 Thread Adam Jackson
On Thu, 2017-10-19 at 15:02 -0700, Alan Coopersmith wrote: > On 10/19/17 01:18 PM, Tobias Stoeckmann wrote: > > If the environment variable HOME is empty, XauFileName triggers an > > out of boundary read access (name[1]). If HOME consists of a single > > character relative path, the output becomes

Re: [PATCH libXau] Avoid out of boundary read access

2017-10-20 Thread Alan Coopersmith
On 10/20/17 12:47 AM, walter harms wrote: Am 19.10.2017 22:18, schrieb Tobias Stoeckmann: If the environment variable HOME is empty, XauFileName triggers an out of boundary read access (name[1]). true but if HOME="" perhaps we could simply return If HOME consists of a single character

Re: [PATCH libXau] Avoid out of boundary read access

2017-10-20 Thread walter harms
Am 19.10.2017 22:18, schrieb Tobias Stoeckmann: > If the environment variable HOME is empty, XauFileName triggers an > out of boundary read access (name[1]). true but if HOME="" perhaps we could simply return If HOME consists of a single > character relative path, the output becomes

Re: [PATCH libXau] Avoid out of boundary read access

2017-10-19 Thread Alan Coopersmith
On 10/19/17 01:18 PM, Tobias Stoeckmann wrote: If the environment variable HOME is empty, XauFileName triggers an out of boundary read access (name[1]). If HOME consists of a single character relative path, the output becomes unexpected, because "HOME=a" leads to "a.Xauthority" instead of

[PATCH libXau] Avoid out of boundary read access

2017-10-19 Thread Tobias Stoeckmann
If the environment variable HOME is empty, XauFileName triggers an out of boundary read access (name[1]). If HOME consists of a single character relative path, the output becomes unexpected, because "HOME=a" leads to "a.Xauthority" instead of "a/.Xauthority". Granted, a relative HOME path leads to