Re: Unclear how to use the command line tool /usr/bin/elog, posted by Stefan Ritt on Thu Dec 9 10:33:09 2021
|
Have you tried to connect directly to elogd and not going through Apache?
| Jose Caballero wrote: |
|
Thanks for the comments. I will pass them to the admins.
|
|
|
Re: Log4j exploit, posted by Stefan Ritt on Tue Dec 14 21:55:16 2021
|
ELog does not use the Log4j library so no issue there. If you run a web server like Apache in front of ELog, you however have to check if you use log4j there.
| Alan Grant wrote: |
|
Is there any potential impact/concern with the Log4j exploit in Elog applications?
|
|
|
Re: Adjustment of summary columns, posted by Stefan Ritt on Fri Dec 17 12:11:22 2021
|
You can manually modify the CSS style to adjust column widths. Locate elog.css which resides under elog/themes/default/elog.css, then find the class “.listtitle”, and modify the line
width: 0%;
to something like
width: 10%;
you can play with the width until it suits your needs. After each change, you have to reload the page in the browser to see the effect.
If you only want to change the width of a specific column, add following lines to your elog.css:
.listtitle:nth-child(4) {
width:30%;
}
where ‘4” is for example the 4th column. You can have several of these statements for different columns.
To hide the text, use the option 'summary lines' as described in the manual.
| Mariia Fedkevych wrote: |
|
Hi!
Is it possible to manage the column widths on a logbook's summary page one by one?
Also, is it possible to hide the Text column without actually hiding the text body in entries (as Show Text = 0 in elog.cfg does)?
Kind regards,
Mariia
|
|
|
Re: elog@Ubuntu 18.04, posted by Stefan Ritt on Mon Jan 31 09:10:41 2022
|
Looks like you don't have shared libraries correctly configured on your system. Try "ldconfig" on your system or link elogd statically (google how to do that).
Stefan
| Carsten Winkler wrote: |
|
Hello,
I try to start elog at Ubuntu 18.04. When I run sudo /usr/local/sbin/elogd -D -c /usr/local/elog/elogd.cfg I get following error:
/usr/lib/libssl.so.10: version `libssl.so.10' not found (required by /usr/local/sbin/elogd)
I checked following:
ls -l /usr/lib/libssl.so.10
lrwxrwxrwx 1 root root 41 Jan 29 08:24 /usr/lib/libssl.so.10 -> /usr/lib/x86_64-linux-gnu/libssl.so.1.0.0
ls -l /usr/lib/x86_64-linux-gnu/libssl.so.1.0.0
-rw-r--r-- 1 root root 424664 Aug 24 18:16 /usr/lib/x86_64-linux-gnu/libssl.so.1.0.0
What's going wrong? And how to solve the problem?
Best,
Carsten
|
|
|
Re: Default "Author" when replying to a log entry, posted by Stefan Ritt on Tue Feb 1 15:43:00 2022
|
As you can see, on this forum the author for replies is correct. This is done via the config option:
Preset on reply Author = $long_name
| Jan Just Keijser wrote: |
|
what is the default value for "Author" when replying to a log entry ? I now see that for each reply to a log entry, the value of "Author" is set to the value of the author of the original entry - this makes it very hard to see which user has replied to a particular log entry, especially when users start replying to replies etc.
This is with elog 3.1.4-3 on CentOS 7
|
|
|
Re: make all messages on ubuntu LTS 20.04.03, posted by Stefan Ritt on Tue Feb 8 09:14:25 2022
|
> /usr/include/x86_64-linux-gnu/bits/stdio2.h:36:10: note: ‘__builtin___sprintf_chk’ output 2 or more bytes (assuming 4097) into a
> destination of size 4096
Yeah, I like those warnings "up to 4097 bytes written to a buffer of 4096 bytes". And it's even not a security issue, since the source of the data comes from elogd.cfg which only the owner can modify.
Basically this calls to rewrite elog completely with std::string. Maybe one day I retire and have some time for that...
Stefan |
|
Re: Password File Config Issue, posted by Stefan Ritt on Thu Feb 10 14:02:15 2022
|
Can you try the "top groups" option, which means putting each logbook into a separate top group as described in the documentation. For us this works well, new users are only added to the right password file. There is however the problem that as admin you might be logged in to several logbooks (as remembered in your browser via cookies), so you might want to log out from all logbooks first (or clear all cookies of elog), then log in to one logbook and add the user there. In worst case you still can modify the password file by hand, they are plain ASCII files. Only the password has to be entered later since it's encrypted.
Stefan
| Mark Delaney wrote: |
|
I expanded an elog server from 1 to 3 logbooks. For each logbook there is a separate password file defined.
When I try to add a new user in one of the 2 new logbooks using config => new user, it adds the user to the password file for the original logbook.
Have verified that access to the logbooks is controlled via the separate password files. If it would help to provide an example of the elogd.cfg or if I need to clarify further, let me know.
Any suggestions welcome.
Thanks. Mark.
|
|
|
Re: "New User" option does not work when Authentication=Webserver, posted by Stefan Ritt on Thu Feb 10 17:32:42 2022
|
Thanks for your patch, I committed it.
Stefan |