elog root path, posted by Antonio Bulgheroni on Thu May 5 11:14:20 2022
|
Dear all,
I have a question for you. On my elog server I have plenty of images not included in any logbook entry, but that nevertheless I would the user
to have access to that via the browser. In order words, I would like to have a link like this https://myelog/my_pics_folder/my_pic.png |
|
Vulnerability?, posted by Alessandro Petrolini on Thu Mar 3 08:26:40 2022
|
Hi, I have been using elog for years at CERN.
Now I installed in my local workstation at my home inistitue
and sysadmin reported the following vulnerabilities: |
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 Alessandro Petrolini on Fri Mar 4 08:51:24 2022
|
Ok, many many thanks!
I will pass the info to my sysadmin.
Best Regards.
|
|
Re: Vulnerability?, posted by Alessandro Petrolini on Sun Mar 6 09:00:33 2022
|
> Ok, many many thanks!
> I will pass the info to my sysadmin.
> Best Regards.
|
|
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?
|
|
Re: Vulnerability?, posted by Stefan Ritt on Mon Mar 7 08:49:41 2022
|
> I trust Stefan is reading this thread and will do something about it. My vote would
> be to remove the download link to the windows executables and ask Debian to remove
> the elog package. I think they have a way for upstream developers (Stefan) to request
|
|
Re: Vulnerability?, posted by Daniel Pfuhl on Mon Mar 7 14:30:16 2022
|
>
> Yeah, I have to recompile the Windows version. Unfortunately my old Windows PC is gone, I
|
|
Re: Vulnerability?, posted by Jan Just Keijser on Mon Mar 7 17:46:39 2022
|
> > I trust Stefan is reading this thread and will do something about it. My vote would
> > be to remove the download link to the windows executables and ask Debian to remove
> > the elog package. I think they have a way for upstream developers (Stefan) to request
|
Re: Vulnerability?, posted by Jan Just Keijser on Wed Mar 9 17:55:31 2022 
|
I've built the last C version of elog in git, revision 1ebfd06c using mingw-64 ; the resulting binaries work for me on Windows 2019.
Attached is a zip file with the binaries.
I was not able to create a new installer, these are just the executables |
|
Re: Vulnerability?, posted by Daniel Pfuhl on Tue Apr 19 15:47:59 2022
|
> I've built the last C version of elog in git, revision 1ebfd06c using mingw-64 ; the resulting binaries work for me on Windows 2019.
> Attached is a zip file with the binaries.
> I was not able to create a new installer, these are just the executables
|
|
Re: Vulnerability?, posted by Jan Just Keijser on Tue Apr 19 17:02:57 2022
|
> > I've built the last C version of elog in git, revision 1ebfd06c using mingw-64 ; the resulting binaries work for me on Windows 2019.
> > Attached is a zip file with the binaries.
> > I was not able to create a new installer, these are just the executables
|
|
Re: Vulnerability?, posted by Daniel Pfuhl on Tue Apr 19 20:13:04 2022
|
> > > I've built the last C version of elog in git, revision 1ebfd06c using mingw-64 ; the resulting binaries work for me on Windows 2019.
> > > Attached is a zip file with the binaries.
> > > I was not able to create a new installer, these are just the executables
|
|
Re: Vulnerability?, posted by Jan Just Keijser on Fri Apr 22 17:10:24 2022
|
> > > > I've built the last C version of elog in git, revision 1ebfd06c using mingw-64 ; the resulting binaries work for me on Windows 2019.
> > > > Attached is a zip file with the binaries.
> > > > I was not able to create a new installer, these are just the executables
|
|
Re: Vulnerability?, posted by Laurent Jean-Rigaud on Mon Mar 7 22:07:54 2022
|
> > I trust Stefan is reading this thread and will do something about it. My vote would
> > be to remove the download link to the windows executables and ask Debian to remove
> > the elog package. I think they have a way for upstream developers (Stefan) to request
|
|
Re: Vulnerability?, posted by Florian Heigl on Mon Apr 18 19:16:36 2022
|
> > I trust Stefan is reading this thread and will do something about it. My vote would
> > be to remove the download link to the windows executables and ask Debian to remove
> > the elog package. I think they have a way for upstream developers (Stefan) to request
|
|
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 Tue Apr 26 17:39:49 2022
|
> > > debian package still outdated?
> removed from debian-unstable
> https://tracker.debian.org/pkg/elog
|
|
history of long-removed freebsd package, Re: Vulnerability?, posted by Konstantin Olchanski on Tue Apr 26 18:03:03 2022
|
> > > > debian package still outdated?
the freebsd elog package was removed back in 2014 during
|
|
Re: Vulnerability?, posted by Konstantin Olchanski on Wed Apr 27 19:36:25 2022
|
> next is to request removal of ubuntu package.
contacted ubuntu security team, got very quick response.
|
Re: Vulnerability?, posted by Andreas Luedeke on Fri Apr 22 12:55:21 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, and the debian package still outdated?
|
|
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:
|
|
Download attachments from command line, posted by Maarten de Jong on Sat Apr 16 10:37:24 2022
|
| Would it be possible to download attachments (e.g. with elog or wget) from the command line? |
|
Re: Download attachments from command line, posted by Stefan Ritt on Tue Apr 19 10:24:47 2022
|
Sure. Just figure out the URL from your browser and then use it in wget, e.g.
wget https://elog.psi.ch/elogs/Forum/220309_175728/elog-3.1.4-1ebfd06c-win64.zip
to download one attachement from this forum. |
|
Re: Download attachments from command line, posted by Maarten de Jong on Thu Apr 21 14:19:35 2022
|
Thanks - I can confirm that the given command works.
However, for an e-log with username and password protection, this no longer seems to work.
It would be very useful if the elog command can be used to also download attachments (and not only a message). |
|
recovery of elog from backup disk, posted by neerajan nepal on Wed Apr 13 16:31:27 2022
|
Hello,
I do have a backup of elog repository in an external disk (with a directory name .elog). I want to install this repository to a new linux (either
ubuntu 20.xx or Cent OS 7) computer. I am new to this, can someone please provide me an instructions sheet. |
|
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: recovery of elog from backup disk, posted by neerajan nepal on Thu Apr 21 03:45:20 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:
|
|
Dynamic substitution with date , posted by Antonio Bulgheroni on Wed Apr 20 14:19:08 2022
|
Dear all,
I would need your help with an incremental index with date information.
I want to have an incremental number made by the last two digits of the year, the two digits of the month and an incremental four digits number. |
|
"User stamp" icon like Time Stamp in Body, posted by Gys Wuyts on Tue Apr 12 08:55:55 2022
|
Hello,
Is there a possibility to use like the time stamp a user stamp: by clicking the button in the main text entry it adds the username, just like
the time stamp button does: Tue Apr 12 08:58:46 2022 ? |
crash with attachment with very long filename, posted by Stefano Lacaprara on Fri Mar 25 10:07:37 2022
|
Hi,
I'm running
elogd 3.1.4 built Jan 27 2021, 09:56:34 revision 395e101a
|
|
Re: crash with attachment with very long filename, posted by Stefan Ritt on Mon Mar 28 14:04:18 2022
|
Hi Stefano,
well, why in heaven's name do you run 200+ chars file names? I see that they are generated probably automatically, but I guess you will run in all kinds |
|
Re: crash with attachment with very long filename, posted by Stefano Lacaprara on Tue Mar 29 11:31:55 2022
|
Hi Stefan,
|
Unformatted Appearance of Elog, posted by Greg Christian on Thu Mar 17 18:22:37 2022
|
I recently ported an elog over to a new server running Ubuntu 20.10. Everything is working okay, except sometimes I get a strange unformatted appearance
when I go to the elog page (see attachment). The happening of this seems random. For example, yesterday, when I started the elogd daemon everything looked
fine, but when I log in today I get the unformatted appearance. Also, yesterday when I was setting things up, sometimes certain logbooks would have the |
|
Re: Unformatted Appearance of Elog, posted by Greg Christian on Tue Mar 22 17:58:32 2022
|
In trying to fix this, I have re-downloaded the source from github rather than the source at http://elog.psi.ch/elog/download/tar/elog-latest.tar.gz,
which is apparently very different from what is on github. Now I am running ELOG V3.1.4-d828aa58 |