| ID |
Date |
Icon |
Author |
Author Email |
Category |
OS |
ELOG Version |
Subject |
|
69460
|
Mon Jan 31 09:10:41 2022 |
 | Stefan Ritt | stefan.ritt@psi.ch | Question | Linux | 3.1.4-3 | Re: elog@Ubuntu 18.04 |
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
|
|
|
69463
|
Tue Feb 1 15:43:00 2022 |
| Stefan Ritt | stefan.ritt@psi.ch | Info | Linux | 3.1.4-3 | Re: Default "Author" when replying to a log entry |
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
|
|
|
69468
|
Tue Feb 8 09:14:25 2022 |
| Stefan Ritt | stefan.ritt@psi.ch | Bug report | Linux | cb3afcd826d26bf | Re: make all messages on ubuntu LTS 20.04.03 |
> /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 |
|
69469
|
Thu Feb 10 14:02:15 2022 |
| Stefan Ritt | stefan.ritt@psi.ch | Question | Linux | ELOG V3.1.4-395 | Re: Password File Config Issue |
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.
|
|
|
69470
|
Thu Feb 10 17:32:42 2022 |
| Stefan Ritt | stefan.ritt@psi.ch | Bug report | Linux | 3.1.4-2 | Re: "New User" option does not work when Authentication=Webserver |
Thanks for your patch, I committed it.
Stefan |
|
69473
|
Tue Feb 15 13:45:02 2022 |
| Stefan Ritt | stefan.ritt@psi.ch | Bug report | Linux | cb3afcd826d26bf | Re: make all messages on ubuntu LTS 20.04.03 |
Well, I bit the bullet and fixed all of these warnings. Took me like two days of work, but now should be fine. You might want to test it again. I only have gcc 9.2.0, there it compiles now without warning.
Stefan |
|
69475
|
Wed Feb 16 08:45:15 2022 |
| Stefan Ritt | stefan.ritt@psi.ch | Bug report | Linux | cb3afcd826d26bf | Re: make all messages on ubuntu LTS 20.04.03 |
I fixed these as well, please have a look again. BTW, midas had a few of these as well.
Stefan |
|
69488
|
Mon Mar 7 08:49:41 2022 |
| Stefan Ritt | stefan.ritt@psi.ch | Question | Windows | 3.1.4-a04faf9f | Re: Vulnerability? |
> I trust Stefan is reading this thread and will do something about it. My vote would
> be to remove the download link to the windows executables and ask Debian to remove
> the elog package. I think they have a way for upstream developers (Stefan) to request
> removal of unmaintained out-of-date insecure versions of their stuff. ROOT
> was in the same situation years ago, the Debian package for ROOT was very old version,
> also built incorrectly, and everybody complained to us that our stuff does
> not work (midas, rootana, etc).
Yeah, I have to recompile the Windows version. Unfortunately my old Windows PC is gone, I
switched now completely to MacOSX and Linux. Probably have to borrow something from somewhere.
If anybody can compile the Windows version with the current source code I would be happy.
Stefan |