How to prevent file path leaks on a 404 page, posted by Rich Loring on Tue May 12 15:53:17 2020
|
Hello,
We used the Elog RPM binary installation method to install Elog. Our security scanners are complaining that Elog discloses the version information
when you hit a missing page (404 error). How can I hide this version info? Is there a snippet of code somewhere that I can comment out? |
Re: How to prevent file path leaks on a 404 page, posted by Stefan Ritt on Tue Aug 4 13:44:01 2020
|
I removed the version info from the 404 error, but you have to recompile elogd from sources. The fix will be included in the next RPM, but that can usually
take a few weeks.
Rich |
|
Re: How to prevent file path leaks on a 404 page, posted by Stefan Ritt on Wed Aug 26 20:44:38 2020
|
A new RPM has been released at https://elog.psi.ch/elog/download/RPMS/elog-3.1.4-2.el7.x86_64.rpm containing that fix.
Stefan
Ritt wrote:
I removed the version info from the 404 error, but you have to recompile |
SSL does not work, posted by Hisataka YOSHIDA on Fri Jun 5 03:49:20 2020
|
Hello.
I installed the latest elog (3.1.4-2) in CentOS 7, and it is working well without SSL.
When I enalbled SSL option (SSL = 1) in the "elogd.cfg", and tried to start the elogd, the message below was shown and failed to run. |
|
Re: SSL does not work, posted by Stefan Ritt on Fri Jun 5 13:24:01 2020
|
When you compile elog from the soruces, you need the OpenSSL library to be installed. The CMake build process will then find it and include it in the
compile process. When you use the "make" build process, you have to make sure that SSL is enabled there:
USE_SSL = 1 |
|
Re: SSL does not work, posted by Hisataka YOSHIDA on Thu Jun 11 08:23:01 2020
|
Dear Stefan,
Thank you for your comment. I successfuly compiled the latest elog from source code, and now elogd could work with SSL.
In fact, I reported the case of installation with rpm file. Maybe, the latest elog rpm doesn't support SSL, I guess. |
|
Re: SSL does not work, posted by Stefan Ritt on Wed Aug 26 20:41:50 2020
|
Today I succeeded with the help of L.JR to produce a new RPM which contains SSL, KRB5, PAM and LDAP support. It's uploaded to https://elog.psi.ch/elog/download/RPMS/elog-3.1.4-2.el7.x86_64.rpm
Hisataka
YOSHIDA wrote:
Dear Stefan, |
do some changes on .CFG, posted by Lahreche Abdelmadjid on Mon Aug 17 10:34:32 2020 
|
Hi All,
I would like to have "Permis de verouillage et d'étiquetage 016685-68AF-0031" when I select it.
I don't found where can I make this change |
|
Re: do some changes on .CFG, posted by Andreas Luedeke on Mon Aug 17 13:27:09 2020
|
This has nothing to do with the ELOG package, but only with your local configuration of that specific logbook.
You should contact your local ELOG administrator.
Or you might want to rephrase you question: do you want to have this text added in the text field when selecting the field specifier? |
|
Re: do some changes on .CFG, posted by Lahreche Abdelmadjid on Tue Aug 18 11:28:58 2020
|
Thanks, but I'm the Admin of local ELOG.
usually I can make a lot of changes on my files .CFG But this time no way.
when I select one of the choice i've a text who appear with the right text (code), but only with this choice "Permis de verouillage |
|
Re: do some changes on .CFG, posted by Andreas Luedeke on Wed Aug 19 15:22:58 2020
|
How are we supposed to give you a hint when you don't post your configuration?
Lahreche
Abdelmadjid wrote:
Thanks, but I'm the Admin of local ELOG. |
|
Reverse sort by Attribue, but it's only showing the last 6 entries by default., posted by Anthony on Sun Aug 9 03:41:05 2020
|
Hi,
I'm trying to use the Sort Attributes option to sort all entries by a user specified date. The issue I'm running into, is that |
|
Re: Reverse sort by Attribue, but it's only showing the last 6 entries by default., posted by Andreas Luedeke on Sun Aug 9 20:47:05 2020
|
It is described in the manual at https://elog.psi.ch/elog/config.html#general
Entries per page = <number>
Funnily the default is "20". I have no idea why you see 6 entries. |
|
Re: Reverse sort by Attribue, but it's only showing the last 6 entries by default., posted by Anthony on Mon Aug 10 09:01:24 2020
|
Thank you, Andreas! Not sure why I kept overlooking it in the manual. As for the number of entries when I sort, I'm not sure. I'll
set it up to display a larger number and see what happens.
Andreas |
SSL connection drop with large content, posted by HyonSan Seo on Mon Aug 10 07:56:43 2020
|
Dear all,
I had some difficulty to upload large files (>20MB) with SSL connection. I think it is also related to https://elog.psi.ch/elogs/Forum/68636 |
|
Re: SSL connection drop with large content, posted by Stefan Ritt on Mon Aug 10 08:33:42 2020
|
Your solution sounds quite good, I will incorporate them in the distribution.
Stefan
HyonSan |
|
Record ID corruption, posted by Frank Baptista on Sun May 3 15:58:24 2020
|
Hi all,
I've encountered an occasional problem that seems to be exacerbated by having a message with many replies.
In our use of ELOG, we run lengthy environmental tests (often several days) in multiple temperature chambers (one logbook for each chamber). |
|
Re: Record ID corruption, posted by David Pilgram on Sun May 3 18:05:32 2020
|
Hi,
I've had problems in the past due to a dodgy pointer creating branches despite a "No branches" in the configuration file.
It would be very interesting to see what the 200428a.log file looks like with these entries: in the screenshot they appear to be shown in time order, but |
|
Re: Record ID corruption, posted by Frank Baptista on Sun May 3 22:43:12 2020
|
Hi David,
Thanks for the quick response! Well, I'd have to say that the sequence is as tangled as it looks in the logbook -- I've attached
a copy of the log file for your reading pleasure. |
|
Re: Record ID corruption, posted by David Pilgram on Mon May 4 14:55:53 2020
|
Hi Frank,
There are two interesting points about the log file.
1. Entry 5658 is timestamped later than 5659, but is earlier in the entry list. It also is "In Reply to" 5659. despite |
|
Re: Record ID corruption, posted by Frank Baptista on Fri May 22 21:03:05 2020
|
Hi David,
Well, you've made some very interesting observations, and raised some excellent questions. So, I went back and did some homework, reviewing
a number of logbooks to find instances where this strange 'record twist' occurs. You had asked, "Do you have enough information to decided |
|
Re: Record ID corruption, posted by David Pilgram on Sat May 23 16:15:38 2020
|
Hi Frank,
Good bit of detective work. To me it suggests that something as yet undetermined occurs, that, when the 57th reply happens, causes the
issue. If that "something" hasn't happened, all is well. Apart from Heinz varieties (not true, in fact), 57 isn't an obvious |
|
Re: Record ID corruption, posted by Stefan Ritt on Tue Aug 4 13:38:05 2020
|
I tried to reproduce the problem with a fresh minimal logbook (the demo one coming from the distribution). Made 60 replies and all went well. So I wonder
if it has to do with some special settings in elogd.cfg. Can you reproduce the problem with an empty logbook and an edlog.cfg which contains just the minimal
settings? |
|
Search feature in ELOG, posted by Illam Pakkirisamy on Sun Aug 2 18:45:18 2020
|
Hi,
Is there a search feature in ELOG. Basically, we have the topics broken up by categories but within the categories we would like to search
by a key word based on the subject to get to a specific topic. |
|
Re: Search feature in ELOG, posted by Andreas Luedeke on Mon Aug 3 13:25:50 2020
|
That question screams: please read the manual! Find command: https://elog.psi.ch/elog/userguide.html#browse
Some simple examples:
https://elog.psi.ch/elogs/Forum/?mode=threaded&reverse=0&reverse=1&npp=20&Subject=Search
https://elog.psi.ch/elogs/Forum/?mode=summary&reverse=0&reverse=1&npp=8&Subject=category
Illam Pakkirisamy |
|
Missing log files when rsync to replacement server., posted by VUIIS SysAdmin on Thu Jul 30 17:11:05 2020
|
I am moving from a Hyper-V host to a VMware host and created a new elog server. I installed the elog software and did an rsync to get the .cfg file and
logbooks to the new server.
rsync -av root@old.elog.server:/usr/local/elog /usr/local/ |
|
Re: Missing log files when rsync to replacement server., posted by Stefan Ritt on Fri Jul 31 15:42:55 2020
|
Start your new server interactively with "elogd -v 3" to see all verbose output. You will then see how it indexes all logbooks. If not, you
might have a wrong path in elogd.cfg
VUIIS |
|
Re: Missing log files when rsync to replacement server., posted by VUIIS SysAdmin on Fri Jul 31 21:40:02 2020
|
On the new server in the logbook that should have several 2020 entries it stops on the last entry of 2019.
On the old server after stopping elogd i get:
/usr/sbin/elogd -v 3 |
|
Re: Missing log files when rsync to replacement server., posted by Stefan Ritt on Sat Aug 1 15:13:17 2020
|
You can put your files where ever you want, just tell elogd where to find the elogd.cfg file via the "-c" flag. Then tell elogd where to find files
in the elogd.cfg file via the "Logbook dir" and "Resource dir" directives.
Stefan |
|
Re: Missing log files when rsync to replacement server., posted by VUIIS SysAdmin on Sun Aug 2 02:57:59 2020
|
Thank-you. That is good information to have.
What is the default if you you do not specify anything in elogd.cfg? I assume it is /usr/local/elog otherwise it would not see the existing
logbooks. |
|
Re: Missing log files when rsync to replacement server., posted by Stefan Ritt on Sun Aug 2 09:06:46 2020
|
If nothing is specified elogd looks for logbooks in the current directory where it got started under ./logbooks/
No idea what happened to your 2020 logbook.
VUIIS |