Have a look at 

http://kb.mozillazine.org/Links_to_local_pages_don't_work

_{We have since discovered that the security team is scanning the box in question once a week when the service crashes, with nexpose.}

_{So if you see something similar then you might want to explore that.}

Probably some very strange URL form nexpose to trigger a potential buffer overflow. If I get the precise URL which crashes elogd, I can reproduce and fix it.

Otherwise my usual advice: Run elogd behind an Apache proxy and do the authentication there. This way nexpose does not get to elogd, it will stop at the Apache (without the proper credentials).

Steafn

> I'd suggest that the "-v" option hide passwords. If they need to be revealed for debugging

As a work around, I've changed the elogd startup script to do:

        /usr/local/sbin/elogd -v -c /usr/local/elog/elogd.cfg 2>&1 | perl -ne '$|=1; if ( $_ =~ /name="upassword"/
) {<>; <>;} else { print "$_";}' > /var/log/elog 2>&1 &

That simply throws away lines that match the pattern:

    name="upassword"

and the following 2 lines (the last of which contains the password).

Hi Janusz,

You can change the following line in elogd.h and recompile:

#define MAX_N_LIST      100
That'll change the login user list limit. But it'll change other list length as well - which should not do harm unless you are very short of memory.

I don't see the Admin user list limit of 10 - aparently that is hard coded somewhere deep within (or I've just missed it).

Cheers, Andreas

Thanks, good point, I was not sure that in case of other lists which will be changed as well, there will not be any problems, like overflow, etc. 

Regarding admin list, now I remember, that was the limit to send email notification in case of registration requests. But actually it is not important right now.

best

Janusz

Well, many arrays based on MAX_N_LIST are created on the heap memory, and if you exceed that, elogd simply crashes. There are compile options to increase the stack and heap size, but that depends on the operating system and the compiler. The value of 100 has been proven to work everywhere. If you increase it, you're on your own.

Stefan