Re: opening a local html file, posted by Stefan Ritt on Mon Oct 22 17:38:32 2007
|
Have a look at
http://kb.mozillazine.org/Links_to_local_pages_don't_work |
|
Re: once a week we are having elogd segault?, posted by mathew goebel on Wed Aug 6 17:08:46 2025
|
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.
mathew |
|
Re: once a week we are having elogd segault?, posted by Stefan Ritt on Thu Aug 7 11:04:39 2025
|
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 |
|
Re: ok i give up - i have to admit - i do not understand the instructions, posted by Stefan Ritt on Thu Apr 19 07:41:19 2007
|
[quote="marion"]is there a possibility to get instructions in newbie language?[/quote]
No. You need some basic knowledge to run elog. Without this knowledge, it's better if you use some other package. |
|
Re: obfuscate password in verbose logging, posted by Mark Bergman on Fri Apr 27 00:29:56 2012
|
> I'd suggest that the "-v" option hide passwords. If they need to be revealed for debugging
|
|
Re: number of entries in Login user list, posted by Andreas Luedeke on Thu Jun 14 12:37:22 2018
|
Hi Janusz,
You can change the following line in elogd.h and recompile:
#define MAX_N_LIST 100 |
|
Re: number of entries in Login user list, posted by Janusz Szuba on Thu Jun 14 13:07:32 2018
|
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. |
|
Re: number of entries in Login user list, posted by Stefan Ritt on Thu Jun 14 13:17:33 2018
|
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. |