Demo Discussion
Forum Config Examples Contributions Vulnerabilities
  Discussion forum about ELOG, Page 403 of 808  Not logged in ELOG logo
ID Date Icon Author Author Emaildown Category OS ELOG Version Subject Text Attachments
  69481   Wed Mar 2 23:15:11 2022 Reply Konstantin Olchanskiolchansk@triumf.caBug reportLinuxELOG V3.1.4-cb3Re: Invalid activation code> Something is not right with the elog account
activation...
  
  69484   Thu Mar 3 16:49:40 2022 Reply Konstantin Olchanskiolchansk@triumf.caQuestionWindows3.1.4-a04faf9fRe: Vulnerability?The CVEs you refer to are very old and have
been fixed a long time ago.
  
  69487   Sun Mar 6 17:33:04 2022 Reply Konstantin Olchanskiolchansk@triumf.caQuestionWindows3.1.4-a04faf9fRe: Vulnerability?> > > The CVEs you refer to are very old and
have been fixed a long time ago.
  
  69498   Fri Mar 18 00:36:37 2022 Warning Konstantin Olchanskiolchansk@triumf.caBug reportLinuxELOG V3.1.4-2e1http status 200 returned for "file not found""file not found" should return http code 404.
elogd returns code 200 together
with a page containing text "404 not found".
  
  69508   Mon Apr 18 21:01:23 2022 Reply Konstantin Olchanskiolchansk@triumf.caQuestionLinuxnot knownRe: recovery of elog from backup diskunfortunately instructions do not exist to
cover every possible situation.
  
  69513   Tue Apr 19 21:15:19 2022 Reply Konstantin Olchanskiolchansk@triumf.caQuestionWindows3.1.4-a04faf9fRe: Vulnerability?> it would be good if the current state was
listed in https://elog.psi.ch/elogs/Vulnerabilities/
> It seems there's now updated builds for
  
  69520   Fri Apr 22 21:15:37 2022 Reply Konstantin Olchanskiolchansk@triumf.caQuestionWindows3.1.4-a04faf9fRe: Vulnerability?> > debian package still outdated?
> We reached to the package maintainer
  
  69521   Sat Apr 23 18:05:57 2022 Reply Konstantin Olchanskiolchansk@triumf.caQuestionWindows3.1.4-a04faf9fRe: Vulnerability?> The CVEs you refer to are very old and have
been fixed a long time ago.
  
ELOG V3.1.5-3fb85fa6