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 |
|
While mirroring, data fields not preserved, posted by Rob Calkins on Tue Oct 26 01:21:01 2021
|
While running two e-log books that were mirrored, I ended up with the situation of two entries with the same number/id. The mirroring did what
it said it would, increment the local logbook entry and grab the entry from the remote logbook. However, when it did, it did not preserve the fields in
the log book that are specified in the config file such as "Author", "Priority", "Subject" ect. I ended up with a very |
|
Too many open files - issue?, posted by Rob Calkins on Fri Oct 15 23:57:38 2021
|
Has anyone had issues with having too many files open? I'll setup my server and let it go but after a while, I end up with a lot of "cannot
create socket: Too many open files" errors being reported. I have a sync to another e-log going which I suspect is part of the cause since that
e-log server hasn't had this issue. I suspect that there are files being opened, going into some return loop code and then never getting closed. I'm |
|
Re: Too many open files - issue?, posted by Stefan Ritt on Mon Oct 25 13:34:06 2021
|
The code segements you show are from the command line tool elog.c, not the server elogd.c. The tool is called to submit a new message from the command
line. Even if there would be a file not properly closed, it will be closed by the operating system once the program finishes. So no problem of too many
open files there. |
wrong server HTTP status code when login failed, posted by Chris Körner on Thu Oct 21 14:57:14 2021
|
Hi,
I am trying to access elog through a python client (https://github.com/paulscherrerinstitute/py_elog) and found a strage strange behavior which
may be related server side problem. The python script generates get/post messages via the python requests library. This works fine so far and I can view |
|
Re: wrong server HTTP status code when login failed, posted by Chris Körner on Thu Oct 21 15:19:16 2021
|
Seems like I've discovered another bug here related to umlauts in my name. :D
I was submitting this post and forgot to put an icon. Elog seems to have saved a copy of my message, which I could not edit since my username
does not match the bugged name saved for this message. |
|
wrong server HTTP status code when login failed, posted by Chris Körner on Thu Oct 21 15:17:52 2021
|
Hi,
I am trying to access elog through a python client (https://github.com/paulscherrerinstitute/py_elog) and found a strage strange behavior which
may be related server side problem. The python script generates get/post messages via the python requests library. This works fine so far and I can view |
How about string constants in config files?, posted by Andreas Luedeke on Thu Oct 21 11:15:20 2021
|
My config files are often large and use some shell scripting. In these shell scripting part I interact with files and execute scripts in specific folder.
It would be nice to have the ability to define for example a file path once and reuse it in different parts of the config file. It would help to
make config files cleaner. For example: |
Redirect in Execute new needs space after ">", posted by Andreas Luedeke on Thu Oct 21 11:00:46 2021
|
EDIT: forget the tip below. Instead just call script files: inline scripting in the ELOG config shows very strange behavior. Doing the same in external
scripts works reliable.
|
|
How to access PSI Elog data from other web clients , posted by Lin Wang on Wed Oct 13 02:38:34 2021
|
We want to develop separate mobile web pages for the web applications deployed at CSNS accelerator, including the PSI Elog.
In Elog, is there RESTful API or HTTP/JSON or HTTP/XML interface for other web clients to access?
Or is there any workaround? |
|
Re: How to access PSI Elog data from other web clients , posted by Stefan Ritt on Wed Oct 13 08:17:23 2021
|
When elog has been developed, REST did not yet exist. The closest you can get is the RSS API. Just try https://elog.psi.ch/elogs/Forum/elog.rdf
and you see the result for this forum. To write to elog, you can use teh HTTP/HTML interface and mimic a browser. See for example elog:69209
Stefan |
|
Re: How to access PSI Elog data from other web clients , posted by Andreas Luedeke on Thu Oct 21 00:42:42 2021
|
There is a python API to access ELOG via HTTP: https://github.com/paulscherrerinstitute/py_elog
Lin
Wang wrote:
We want to develop separate mobile web pages for the web applications |