SSL, posted by Chris Smyth on Thu Aug 4 14:28:18 2016
|
How do I enable SSL with port 443 in version ELOG V2.7.8-2294 and
rename from localhost?
Server is running Windows 2008 |
Re: Sample of actual elog Config with URL in SSL, posted by Chris Smyth on Thu Aug 4 16:40:14 2016
|
how do I compile elogd with USE_SSL=1?
Andreas Luedeke wrote:
You normally don't need |
|
Re: Sample of actual elog Config with URL in SSL, posted by Chris Smyth on Tue Aug 9 04:23:07 2016
|
By the Makefile i belive you are refering to the elogd.cfg? if not what file do I have use?
I have added
port = 443 |
|
Re: Body Width, posted by Chris Smyth on Mon Sep 12 19:10:03 2016
|
> How do I make this section Wider or Shorter in the 2.7.8 version?
> Maybe I did something to make it shorter? ELCode shows as a full box but plain txt is very short box.
|
Enforcement of password complexity , posted by Chris Smyth on Sat Oct 1 15:32:53 2016
|
Is there a way to enforce password complexity for users?
Either in this version of elog or the newest version? |
Re: Elog ID entry bug at >99999 entries, posted by Chris Rasmussen on Sat May 5 11:22:50 2018 
|
Hi Andreas, I'm working on the same experiment as Joseph who submitted the bug report.
You are right, IDs greater than 10^5 are created no problem. The issue is with the internal elog link, in this case of the form elog:SequencerEvents/XXXXX
The link generated uses only the first 5 digits of the message ID, and therefore links to the wrong message. In the two attachments you can see our sequencer |
|
Re: Elog ID entry bug at >99999 entries, posted by Chris Rasmussen on Mon May 7 18:10:20 2018
|
ah yes, that was a helpful clue. Our elogd.cfg file led me to a .js file which redefines the ID to the elog:SequencerEvents/XXXXX
format and it indeed had a silly hard coded length of that string.
Since I am pretty sure this is our code, I think it is safe to say that this is not a bug in the elog |
outdated debian package, posted by Chris Körner on Fri Dec 18 18:08:54 2020
|
Hi everyone,
I am currently trying to setup elog as a docker container. I wonder if there is any reason why the elog debian package is stuck at version 3.1.3?
Would it be possible to update it to the latest version? |