Re: Invalid activation code, posted by Konstantin Olchanski on Wed Mar 2 23:15:11 2022
|
> Something is not right with the elog account activation...
I did a test:
|
|
Re: Vulnerability?, posted by Konstantin Olchanski on Thu Mar 3 16:49:40 2022
|
The CVEs you refer to are very old and have been fixed a long time ago.
Please refer to:
|
|
Re: Vulnerability?, posted by Konstantin Olchanski on Sun Mar 6 17:33:04 2022
|
> > > The CVEs you refer to are very old and have been fixed a long time ago.
>
> Am I wrong that the windows executable version on the site is dated 2018? 3.1.4-2?
|
http status 200 returned for "file not found", posted by Konstantin Olchanski on Fri Mar 18 00:36:37 2022
|
"file not found" should return http code 404. elogd returns code 200 together
with a page containing text "404 not found". This pollutes the browser cache
with wrong content (in this case, we are trying to load a css file, and the browser
|
|
Re: recovery of elog from backup disk, posted by Konstantin Olchanski on Mon Apr 18 21:01:23 2022
|
unfortunately instructions do not exist to cover every possible situation.
but in general, to migrate elog to a new machine, I would say do this:
|
|
Re: Vulnerability?, posted by Konstantin Olchanski on Tue Apr 19 21:15:19 2022
|
> 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 at least windows
|
|
Re: Vulnerability?, posted by Konstantin Olchanski on Fri Apr 22 21:15:37 2022
|
> > debian package still outdated?
> We reached to the package maintainer
|
|
Re: Vulnerability?, posted by Konstantin Olchanski on Sat Apr 23 18:05:57 2022
|
> The CVEs you refer to are very old and have been fixed a long time ago.
>
> Please refer to:
|