elog command creates always UTF-8 encoded entries, posted by Andreas Luedeke on Wed Jan 19 13:30:48 2011
|
If I create an entry via the web-interface, the defined encoding of the browser is used.
If I create an entry via "elog", it is always stored in UTF-8 encoding.
For the text I can overcome that with HTML encoding, but for attribute values the encoding does not show properly.
|
|
Odd bug with conditional and required attributes, posted by T. Ribbrock on Fri Feb 4 23:48:54 2011
|
I just ran into an odd bug with conditional attributes: If I add a certain attribute to "Required Attributes", none of the conditionals will
work anymore. I have tried to create a small logbook definition that will demonstrate the problem (the original logbook is more complex and uses two sets
of conditionals, both of which will be disabled when the bug hits): |
|
Mail are no longer sent from the logged in user in 2.9.0, posted by Olivier Callot on Wed Mar 23 10:01:01 2011
|
We upgraded to Elog 2.9.0-2402 and since then mails sent by Elog when posting an item are from the default account, not from the logged in user's mail
address.
The configuration is, for the mail part : |
|
Elog 2.9.0 buffer overflow crash bug ubuntu linux, posted by John Rouillard on Sun Apr 10 01:49:01 2011
|
When running openvas (a nessus fork) against elog 2.9.0 I provoked the following crash:
Apr 9 17:32:06 unixland elogd[1300]: POST / HTTP/1.0#015#012Host: unixland.home
|
|
Re: elog 2.8.0 as daemon crashes when editing selected threaded list, posted by Mark Bergman on Thu Apr 21 21:06:20 2011
|
Mark Bergman wrote:
I recently upgraded elog from 2.7.8 to 2.8.0 (and moved servers, removed unused logbooks, etc.). I'm now having a problem |
|
elogd crashes when running mirror cron with SSL and KRB5, posted by Andreas Luedeke on Mon May 30 12:28:53 2011
|
When I run a mirror server and both logbooks using SSL/KRB5 then the cron job causes a segmentation fault.
I haven't tried to check it with a simple configuration yet.
|
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".
|
|
SEGV after upgrade from 2.7.8 to 2.9.0, posted by Kester Habermann on Mon Aug 15 11:36:02 2011
|
Hello,
We've been using ELOG 2.6.5 to 2.7.8 for 4 years without any major problems.
Recently we upgraded to version 2.9.0 and since we've had the daemon frequently crash with SEGV. |