Re: [bug-inetutils] [PATCH] syslogd: Fix possible memory corruption while reading configuration file.

[Alex Kost]

Mats Erik Andersson (2015-04-08 23:47 +0300) wrote:

> Thursday den  2 April 2015 klockan 10:13 skrev Ludovic Courtès detta:
>> address@hidden (Alfred M. Szmidt) skribis:
>> 
>> > Thanks!  I'll read the bug report tomorrow -- I think there is more
>> > than catches the eye.  Leading whitespace before the selector is not
>> > valid syntax for syslog.conf AFAIR.
>> 
>> It?s valid syntax in practice, and that?s one would expect, I think.
>> 
>> > Also, bcopy was marked deprecated in POSIX 2001, and removed in 2008;
>> > memcpy is always prefered.
>> 
>> Oh right, ?memmove? then.
>
> A change set has been pushed to the development head, including
> the change to use memmove(), which POSIX wants us to use, as well
> as an additional test case in the script 'tests/syslogd.sh'.
>
> It is unfortunate that I am unable to reproduce the issue with
> either of Debian GNU/Linux, FreeBSD 10 and OpenIndiana; all the
> more so, since the report of Alex Kost in 'guix-devel' clearly
> demonstrates all details to be seen in an actual failure. I for
> one would be interested in more detail, so as to be able to
> identify some system characteristics, making the corresponding
> libc implementation prone to be sensitive to issued with over-
> lapping string buffers.
>
> Thank your for bringing the issue forward to us.

Perhaps the problem appeared for me because I use a 32bit machine.  Is
there any other information I can provide?

-- 
Alex