segmentation fault when "restrict edit" is used and "new" is allowed for anonymous users, posted by Andreas Luedeke on Mon Jun 20 05:31:31 2011 
|
The simple config file below produces a segmentation fault when elogd is started,
http://localhost/Test/?cmd=New
is opened in the browser and then e.g. "Entry" is switched to "Problem".
|
segmentation fault, posted by Heiko Scheit on Fri Feb 13 12:18:19 2004
|
Around line 2240 (in loc()) in elogd.c the following is written,
which results in an infinite loop, since loc() recursively with
|
|
segfault on empty, non-writable passwd file, posted by Achim Dreyer on Mon Mar 26 13:44:23 2012
|
Segfault when password file is empty and not writable a segmentation fault is generated when a new user tries to register:
|
segfault in auth.c:366, posted by gary holman on Fri Apr 23 04:59:58 2021
|
Elog version: ELOG V3.1.4-611489ba
I am running openldap on the localhost. For some reason now, elogd is segfaulting when (I believe) when a new user is being added to the
password file. For example: |
|
security in find option as a guest, posted by Etienne Van Caillie on Mon Jan 6 19:53:28 2003
|
if you are guest in the find option
select 'all logbook'
|
secure way to allow users create logbook, posted by Szu-Ching Peckner on Tue Aug 28 23:02:07 2012
|
I don't think there is a good secure way so far, but would like to have your opinion.
If I want user to create logbook for themselves, what's the best way to do it? I guess Execute $attribute = <command> may work, have it write |
search and filters in a cookie !?, posted by Emiliano Gabrielli on Mon May 2 12:34:52 2005
|
Is it possible to have last runtime filtering and viewing method to be
stored in a cookie in order to make them permanent across navigation ?
|
|
search and datetime, posted by Arno Teunisse on Wed Jun 10 22:27:08 2009
|
Hello
I have the following in elog.cfg :
Attributes = Author, Author Email, Category, Customer, server, Subject , Change Window Begin , |