Catgegory filtering, posted by Gabriel Lopez on Tue Sep 24 19:38:23 2024
|
Currently have multiple logbooks hosted with elogd. One book is having an issue with Categories. The user regulary uses the category filtering to see
one subject for the whole month. This past week it hasn't been working properly. When choosing a drop down category to filter there are not logs found.
I've notice the fields under the categories change randomly. Sometimes it would add a % sign where there should be --. Some other fields go from displaying |
results of security scan, posted by David Stops on Mon Nov 1 12:52:23 2021
|
Recently central IT scanned our elog server and reported the following "vulnerabilities"
42873 (1) - SSL Medium Strength Cipher Suites Supported (SWEET32)
51192 (1) - SSL Certificate Cannot Be Trusted
65821
(1) - SSL RC4 Cipher Suites Supported (Bar Mitzvah)
85582 (1) - Web Application Potentially Vulnerable to Clickjacking
Is |
Re: results of security scan, posted by Stefan Ritt on Tue Nov 2 12:07:46 2021
|
The elgod.c progarm itself is rather weak in SSL, since I just don't have time to catch up with the latest SSL enhancements. The safest you can do
is to put an industry-strenth web server like Apache in front of elogd and let that server handle the SSL layer.
Stefan |
|
Re: results of security scan, posted by David Stops on Thu Nov 4 13:48:00 2021
|
Thanks, I'll try that and see what happens
David |
Problem with eloglang.german_UTF8, posted by Andreas Luedeke on Tue Aug 7 10:53:45 2018
|
I had a problem with restarting ELOG since about a year, and finally I found the culprit. I just want to share it here, to prevent anyone else to make
the same mistake,
Apparently the files resources/eloglang.* are rather sensitive to the syntax. But it doesn't tell you: no warning or error message comes |
New entry cannot be written to directory "/usr/local/elog/logbooks/demo/", posted by Tapasi Ghosh on Mon Feb 8 13:52:33 2016 
|
Dear All,
I could not submit a new enetry to my logbook whenever restarting my laptop. I am a new user to elog.
Attached is the screenshot of the error message and also there is "nobody" while I grep elog. |
|
Re: New entry cannot be written to directory "/usr/local/elog/logbooks/demo/", posted by Andreas Luedeke on Mon Feb 8 15:07:05 2016
|
You should check if the directory /usr/local/elog/logbooks/demo belongs to the right user and has the right write permissions.
Since the elogd process belongs to the user "nobody", the directory should best belong to "nobody" as well (or - not recommended
- allows write access for "others") |
|
Re: New entry cannot be written to directory "/usr/local/elog/logbooks/demo/", posted by Tapasi Ghosh on Mon Feb 8 16:19:11 2016
|
Thanks for your reply.
I am the user and it also has the write access
cd /usr/local/elog/ |