Enabling SSL, posted by Pasti on Fri May 18 08:04:37 2018
|
Hi all,
I'm following config guide and so far so good. The only issue I run into is when enabling SSL.
Guide says - One can replace this certificate and key with a real certificate to avoid browser pop-up windows warning about the self-signed certificate. |
Re: Enabling SSL, posted by Stefan Ritt on Tue Jun 5 12:28:27 2018
|
This comes from the openSSL library which elog includes. I tried myelf and found that a chained certificate is not correctly interpreted by the openSSL
library. Most people anyhow don't use SSL inside elog, but run an Apache server in front of elog. This is anyhow better since Apache has an industry-strength
security with regular updates. Much better than relying on OpenSSL. |
|
html mode with preset text template cannot be read by newly updated MS-Edge browser, posted by utomoadji wisnubroto on Wed Jun 6 18:25:32 2018
|
i have elog tab configuration with preset text as follow :
=====================================================================
[Shift Entry] |
|
Changing of entries after expired time restriction by synchronisation, posted by Gino Guenzburger on Thu Aug 16 13:33:39 2018
|
I'm working on setting up an elog as lab-journal in our group with the following set-up:
The elog is running on a server, with no back-end access for the users.
Multiple people will use it, all loging in with the
same user-name and password.
The entries submitted to the log-book can only be edited for 24hours, as defined by the "Restrict edit time= |
|
Logfile not registering entry numbers?, posted by Sergio Navarrete on Fri Oct 19 08:38:06 2018
|
I have configured a logbook with the logfile on, but when a user replies to an entry the line logged goes
Date Time [User@IP] {Logbook} NEW entry #0
How can I make the #0 be the real entry number for the reply? |
|
Re: Logfile not registering entry numbers?, posted by Andreas Luedeke on Fri Oct 19 13:08:30 2018
|
It looks like you've found a bug in ELOG. I've checked my elog.log and see that all NEW entry lines show "#0".
I've looked into the code: the message is written before the new entry is submitted, and only then the entry ID is defined.
For
new entries one would need to make the logging print line later - but that would blow up the code.
The message IDs are correct for saving |
|
Re: Logfile not registering entry numbers?, posted by David Pilgram on Mon Oct 29 14:26:28 2018
|
As a regular elog (ab)user, I have seen this behaviour from time to time. So far as I recall, the cause actually is that a normal entry is looking
for the entry in the "Reply to" field of the normal entry in the yymmdda.log file. When that entry does not exist, then I see a duplicate
line of an entry with entry "#0", in emboldened black type. I did have a screenshot, but cannot find it for now. |
Need to change port 25, posted by Yanick Vachon on Mon Nov 26 17:32:31 2018
|
Hi,
We've made changes in our network and now we have to use port 587 instead of port 25, how can i edit that parameter?
Thanks |