Re: bug in elog.spec, posted by Janusz Szuba on Tue Jul 7 11:22:45 2020
|
Thanks for the answer, I will try with your specfile
best
Janusz |
testing the client: unclear it worked, posted by Jose Caballero on Thu Jul 30 17:03:12 2020
|
Hello,
I just gave it a quick try to the command line client, to see if I can use it to access our institution service.
|
|
Re: testing the client: unclear it worked, posted by Stefan Ritt on Fri Jul 31 08:34:35 2020
|
The <hostname> you have to actually replace with your real host name. Same for logbook, username and password.
On my local test system I get (actual password hidden here with "...")
~$ elog -h localhost -p 8080 -l demo -u stefan ... -a Authort=SR -a Subject=test |
|
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 |
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 |
|
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: 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 |