Demo Discussion
Forum Config Examples Contributions Vulnerabilities
  Discussion forum about ELOG  Not logged in ELOG logo
icon4.gif   getcfg problem in v1.410: Truncation of long config strings, posted by Steve Jones on Wed Jul 28 18:25:32 2004 
    icon2.gif   Re: getcfg problem in v1.410: Truncation of long config strings, posted by Stefan Ritt on Wed Jul 28 21:54:36 2004 
       icon14.gif   Re: getcfg problem in v1.410: Truncation of long config strings, posted by Steve Jones on Wed Jul 28 22:07:31 2004 
Message ID: 631     Entry time: Wed Jul 28 22:07:31 2004     In reply to: 630
Icon: Agree  Author: Steve Jones  Author Email: steve.jones@freescale.com 
Category: Bug report  OS: All  ELOG Version: 2.5.4? 
Subject: Re: getcfg problem in v1.410: Truncation of long config strings 
> > Just compiled 1.410 and have run into an issue that *may* have been
> > introduced in 1.393.
> > 
> > Config file directives such as "Welcome title" could be very long strings. 
> > After compiling 1.410, our "Welcome title" is truncated and, while I haven't
> > counted the actual chars, I suspect that the truncation happens at 1024
> > characters.  The procedure 'getcfg' has a declared passed paramater "int
> > vsize". 
> 
> Actually before 1.393 you got a buffer overflow if any string in the
> configuration file was longer than 500 chars, so it's a miracle that your elogd
> did not crash on the long Welcome Title. I added the "vsize" parameter to avoid
> such crashes. To satisfy your need for a long Welcome title, I increased the
> string size for that particular case to 10000 chars. Hope this is enough.

Hmmm, it is a wonder.  Our welcome text was not significantly longer (about 20
chars longer) so perhaps . . . ?

Thanks, will recompile and report back.
ELOG V3.1.5-fe60aaf