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, |
|
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 |
|
Re: Using curl to post new entries, posted by Florian Feldbauer on Wed Sep 2 11:56:04 2020
|
After going through the code of the Python API (https://github.com/paulscherrerinstitute/py_elog/blob/master/elog/logbook.py) I tried the following:
$ python3
>>> from passlib.hash import sha256_crypt |
|
Re: Using curl to post new entries, posted by Stefan Ritt on Wed Sep 2 15:42:40 2020
|
This is correct. The elogd daemon needs username and password in parameters "unm" and "upwd". The password must be SHA256 encoded,
so best is to grab it from the password file. This way one does not have to send clear text passwords over the network.
Florian |
|
Re: field selections persist across new log entries?, posted by Sebastian Schenk on Tue Sep 8 16:35:14 2020
|
As far as I know, it is not possible, if you make a "new" entry.
You could configure the elog, to always PRESET an atribute, but then it is always the same, not the last.
I think the "duplicate" entry function could provide you partly with the functionality you want, as it copies all old values into a |
|
Re: field selections persist across new log entries?, posted by Andreas Luedeke on Wed Sep 9 10:33:58 2020
|
It is probably possible, but requires a big of a hack.
Whenever you save a new entry or edit an old one, you run a little shell script
to write the value of this field into a file.
Whenever you create a new entry you read the PRESET value with a shell script from that file.
Here
are the relevant excepts from the documentation: |
|
Re: Insert images slow downs the ELOG, posted by Andreas Luedeke on Sat Sep 12 19:19:02 2020
|
I found the most limiting factor of ELOG to be the file access. ELOG stores all entries in files and therefore has a lot of disk access.
We found that an AFS directory for ELOG is unusable. We tried to store our logbooks on NFS, and it was barely usable but slow. Now we use a local
disk on the server, that works fine. |
|
Re: testing the client: unclear it worked, posted by Jose Caballero on Mon Sep 14 15:40:02 2020
|
Sorry for the late reply. I didn't get email notification about an answer to my question :)
Actually, I just wrote <hostname> and so on for privacy. In my attempt, they have real values.
And yet, I got as result: "Message successfully |