Crash problems on Solaris, was: Re: [syslog-ng]Security: syslog-ng 1.4.x and 1.5.x is vulnerable to buffer overflow

Balazs Scheidler bazsi@balabit.hu
Thu, 10 Oct 2002 11:09:00 +0200


On Thu, Oct 10, 2002 at 05:41:20PM +0900, Katsuhiro Kondou wrote:
> In article <20021010083117.GC24001@balabit.hu>,
> 	Balazs Scheidler <bazsi@balabit.hu> wrote;
> 
> } This code path is only used _iff_ a HUP is sent to syslog-ng. Is the
> } segfault triggered by sending a HUP to the process, or it is simply crashing
> } without HUP?
> 
> Mine is dead soon after syslog-ng starts, so without SIGHUP.

I've started loading my Sparc server with logs. No crashes so far.

do you have remote sources? (e.g. udp or tcp?)

if yes, which one is loaded?

this is my config now:

source src { udp(port(2000)); sun-streams("/dev/log" door("/etc/.syslog_door")); internal(); };
destination dst { file("/var/log/messages"); };

log { source(src); destination(dst); };

I'm sending messages through udp and from locally as well.

-- 
Bazsi
PGP info: KeyID 9AF8D0A9 Fingerprint CD27 CFB0 802C 0944 9CFD 804E C82C 8EB1