ID |
Date |
Icon |
Author |
Author Email |
Category |
OS |
ELOG Version |
Subject |
69512
|
Tue Apr 19 20:13:04 2022 |
| Daniel Pfuhl | daniel.pfuhl@medizin.uni-leipzig.de | Question | Windows | 3.1.4-a04faf9f | Re: Vulnerability? |
> > > 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
> >
> > I tried to just exchange the attached binaries in my installation but this didn't worked.
> > elogd was not able to start.
>
> hmmm strange - did you get an error message or did the binary simply not start? I've only tested this on a single Windows machine....
Error message is:
Error 1053: The service did not respond to the start or control request in a timely fashion.
I have to admit that I'm doing all this on a Server 2012 machine. |
69511
|
Tue Apr 19 17:02:57 2022 |
| Jan Just Keijser | janjust@nikhef.nl | Question | Windows | 3.1.4-a04faf9f | Re: Vulnerability? |
> > 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
>
> I tried to just exchange the attached binaries in my installation but this didn't worked.
> elogd was not able to start.
hmmm strange - did you get an error message or did the binary simply not start? I've only tested this on a single Windows machine.... |
69510
|
Tue Apr 19 15:47:59 2022 |
| Daniel Pfuhl | daniel.pfuhl@medizin.uni-leipzig.de | Question | Windows | 3.1.4-a04faf9f | Re: Vulnerability? |
> 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
I tried to just exchange the attached binaries in my installation but this didn't worked.
elogd was not able to start.
Regards,
daniel |
69509
|
Tue Apr 19 10:24:47 2022 |
| Stefan Ritt | stefan.ritt@psi.ch | Question | Linux | 3.1.4 | Re: Download attachments from command line |
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.
Stefan
Maarten de Jong wrote: |
Would it be possible to download attachments (e.g. with elog or wget) from the command line?
|
|
69508
|
Mon Apr 18 21:01:23 2022 |
| Konstantin Olchanski | olchansk@triumf.ca | Question | Linux | not known | Re: recovery of elog from backup disk |
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:
- on new machine, install new elog from scratch
- copy the old elogs from "logbooks" on the backup disk to the new elog "logbooks"
- merge the config file by hand (this may require a few tries)
feel free to ask for more help with any of these steps here.
K.O. |
69507
|
Mon Apr 18 19:16:36 2022 |
| Florian Heigl | me@florianheigl.me | Question | Windows | 3.1.4-a04faf9f | Re: Vulnerability? |
> > 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
> > removal of unmaintained out-of-date insecure versions of their stuff. ROOT
> > was in the same situation years ago, the Debian package for ROOT was very old version,
> > also built incorrectly, and everybody complained to us that our stuff does
> > not work (midas, rootana, etc).
>
> Yeah, I have to recompile the Windows version. Unfortunately my old Windows PC is gone, I
> switched now completely to MacOSX and Linux. Probably have to borrow something from somewhere.
> If anybody can compile the Windows version with the current source code I would be happy.
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?
Personally, I don't think removing download links and pulling packages should be more than a temporary measure.
Treating people fairly IMHO means they should be able to reach a safe version by the same means that brought and left them exposed.
A clear central source would be best, one that has
- package autobuilds
- source
- cve list
If I understand correctly, currently only the source is up to date?
(I found py_elog on Github, so it could be an easy option to mirror ELOG there and let some free service handle the autobuilds.
I don't know how well one can flag vulnerabilities there, but likely it's possible, and ideally more people would help there.)
p.s.: My hat is off to the sysadmin who checked carefully, I wanted to introduce ELOG in a windows-centric place and I can't swear I would have checked this (official) download as well. |
69506
|
Sat Apr 16 10:37:24 2022 |
| Maarten de Jong | mjg@nikhef.nl | Question | Linux | 3.1.4 | Download attachments from command line |
Would it be possible to download attachments (e.g. with elog or wget) from the command line? |
69505
|
Wed Apr 13 16:31:27 2022 |
| neerajan nepal | nepal1n@cmich.edu | Question | Linux | not known | recovery of elog from backup disk |
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.
Thank you |