Demo Discussion
Forum Config Examples Contributions Vulnerabilities
  Discussion forum about ELOG, Page 725 of 795  Not logged in ELOG logo
New entries since:Thu Jan 1 01:00:00 1970
ID Date Iconup Author Author Email Category OS ELOG Version Subject
  69488   Mon Mar 7 08:49:41 2022 Reply Stefan Rittstefan.ritt@psi.chQuestionWindows3.1.4-a04faf9fRe: 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.

Stefan
  69489   Mon Mar 7 14:30:16 2022 Reply Daniel Pfuhldaniel.pfuhl@medizin.uni-leipzig.deQuestionWindows3.1.4-a04faf9fRe: Vulnerability?
> 
> 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.
> 
> Stefan

That would be most welcome!
I tried to recompile the windows version a while ago but didn't manage it.
I'm just a simple ELOG __user__ ^^
Looking forward to the new precompiled Windows version.

Thnx in advance!

daniel
  69490   Mon Mar 7 17:46:39 2022 Reply Jan Just Keijserjanjust@nikhef.nlQuestionWindows3.1.4-a04faf9fRe: 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.
> 
> Stefan

FWIW: you could cross-compile on Linux using 
   make CC=x86_64-w64-mingw32-gcc CFLAGS="-D_MSC_VER -DHAVE_VASPRintF -Imxml" LIBS="-Wl,--allow-multiple-definition -ladvapi32 -lwsock32 -lssl -lcrypto"
or so I thought... with build 3.1.4 - 395e101 I did manage, finally. 
However, with the latest git version everything seems to have been renamed to .cxx files (though it's still plain C ??!?!?) and my quick and dirty compile hack did not work. The binaries do work, I can start the server and access it via the web interface.
  69491   Mon Mar 7 22:07:54 2022 Reply Laurent Jean-Rigaudlollspam@free.frQuestionWindows3.1.4-a04faf9fRe: 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.
> 
> Stefan

Hi Stefan,

I don't find any howto to build elog under windows, so i tried to compile elog-latest sources with cygwin (packages gcc + openssl-devel + openldap-devel + make). 
It builds, i could start elogd.exe and connect to localhost:8080 ! 
I generate a zip with cygwin dll needed to launch elogd and tools. I think they could be enclosed (maybe the cygwin licence file have to be added ?).

Btw it should be possible to crossbuild it under Mac or Linux. The problem is to test it ;-). On Mac, you can use UTM to create a Windows VM to do the work.

Bye
Laurent
Attachment 1: elog-3.1.4-395e101.zip
  69493   Wed Mar 9 17:55:31 2022 Reply Jan Just Keijserjanjust@nikhef.nlQuestionWindows3.1.4-a04faf9fRe: 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
Attachment 1: elog-3.1.4-1ebfd06c-win64.zip
  69495   Mon Mar 14 08:49:44 2022 Reply Stefan Rittstefan.ritt@psi.chQuestionLinux3.1.3-7933898Re: Removal of ID and Date attributes

Use the configuration option

List display = Day, Station Type, Start time UTC, ...

as written in the documentation.

Best,
Stefan

James Darrow wrote:

Hello all,

I just found elog which is a great piece  of software! I'm implementing it for use to log my shortwave listening contacts. The problem that I have is I'm moving over a current log to elog which already has a date of when the record was created, which is important.I renamed the old date to day to upload the log into elog. My problem is I don't need to see elog's ID# or date/time stamp of when the log was created seeing it's already in my data. My question is, is there any way to not show elog's ID# and date/time stamp or would I need to create a tab and if so could someone provide a config file where I could see how the tab was implemented. I've attached a screenshot of what it looks like so far. I've implemented the dark theme (which I like) that Anthoney had posted in the contibutions section.

Thanks in advance!

Jim

 

  69496   Mon Mar 14 18:45:14 2022 Reply James Darrowkb9mmc@ameritech.netQuestionLinux3.1.3-7933898Re: Removal of ID and Date attributes

That worked! Thanks Stefan

Stefan Ritt wrote:

Use the configuration option

List display = Day, Station Type, Start time UTC, ...

as written in the documentation.

Best,
Stefan

James Darrow wrote:

Hello all,

I just found elog which is a great piece  of software! I'm implementing it for use to log my shortwave listening contacts. The problem that I have is I'm moving over a current log to elog which already has a date of when the record was created, which is important.I renamed the old date to day to upload the log into elog. My problem is I don't need to see elog's ID# or date/time stamp of when the log was created seeing it's already in my data. My question is, is there any way to not show elog's ID# and date/time stamp or would I need to create a tab and if so could someone provide a config file where I could see how the tab was implemented. I've attached a screenshot of what it looks like so far. I've implemented the dark theme (which I like) that Anthoney had posted in the contibutions section.

Thanks in advance!

Jim

 

 

  69499   Tue Mar 22 17:58:32 2022 Reply Greg Christiangchristian@tamu.eduQuestionLinuxV3.1.4-395e101Re: Unformatted Appearance of Elog

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

The problem still persists, however, although only for some of the logbooks.  Curiously, it *seems* to only show up if I run elogd with the -D flag. If I just run it in the terminal, I have not seen the formatting problem (so far).

In case it's helpful, I post my elodg.cfg file.

 

 

Greg Christian wrote:

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 formatting issue, and I could make this go away with a kill...restart cycle of elogd.

I downloaded the source code from here: https://elog.psi.ch/elog/download.html, selecting the elog-latest.tar.gz file.

I have tried viewing the elog on 3 different browsers (firefox, IE, Edge), result is the same every time.

Any thoughts about what the problem is?

 

Attachment 1: elogd.cfg
[global]
port = 8081
Logbook dir = /data/home/gchristian/packages/elog-3.1.4-3/logbooks
Password file = gcg01.pwd
Admin user = ne21pt

[21Ne_pt]
Theme = default
Comment = 21Ne_pt logbook for the BlueSteAl detector
Attributes = Author, Type, Category, Subject
Options Type = Routine, Software Installation, Problem Fixed, Configuration, Other
Options Category = General, Hardware, Software, Network, Other
Extendable Options = Category
Required Attributes = Author
Page Title = ELOG - $subject
Reverse sort = 1
Quick filter = Date, Type

[BlueSteAl General]
Theme = default
Comment = General logbook for the BlueSteAl detector
Attributes = Author, Type, Category, Subject
Options Type = Routine, Software Installation, Problem Fixed, Configuration, Other
Options Category = General, Hardware, Software, Network, Other
Extendable Options = Category
Required Attributes = Author
Page Title = ELOG - $subject
Reverse sort = 1
Quick filter = Date, Type

[Detectors]
Theme = default
Comment = Detectors logbook for the BlueSteAl detector
Attributes = Author, Type, Category, Subject
Options Type = Routine, Software Installation, Problem Fixed, Configuration, Other
Options Category = General, Hardware, Software, Network, Other
Extendable Options = Category
Required Attributes = Author
Page Title = ELOG - $subject
Reverse sort = 1
Quick filter = Date, Type


[DAQ]
Theme = default
Comment = DAQ logbook for the BlueSteAl detector
Attributes = Author, Type, Category, Subject
Options Type = Routine, Software Installation, Problem Fixed, Configuration, Other
Options Category = General, Hardware, Software, Network, Other
Extendable Options = Category
Required Attributes = Author
Page Title = ELOG - $subject
Reverse sort = 1
Quick filter = Date, Type

[BlueSteAl]
Theme = default
Comment = Detectors logbook for the BlueSteAl detector, 11Be breakup experiment
Attributes = Author, Type, Category, Subject
Options Type = Routine, Software Installation, Problem Fixed, Configuration, Other
Options Category = General, Hardware, Software, Network, Other
Extendable Options = Category
Required Attributes = Author
Page Title = ELOG - $subject
Reverse sort = 1
Quick filter = Date, Type

[mvme_DAQ]
Theme = default
Comment = DAQ logbook for the Mesytec DAQ with BlueSteAl detector
Attributes = Author, Type, Category, Subject
Options Type = Routine, Software Installation, Problem Fixed, Configuration, Other
Options Category = General, Hardware, Software, Network, Other
Extendable Options = Category
Required Attributes = Author
Page Title = ELOG - $subject
Reverse sort = 1
Quick filter = Date, Type


[PPAC]
Theme = default
Comment = PPAC logbook for the BlueSteAl detector
Attributes = Author, Type, Category, Subject
Options Type = Routine, Software Installation, Problem Fixed, Configuration, Other
Options Category = General, Hardware, Software, Network, Other
Extendable Options = Category
Required Attributes = Author
Page Title = ELOG - $subject
Reverse sort = 1
Quick filter = Date, Type


[Phoswich]
Theme = default
Comment = Phoswich logbook for the BlueSteAl detector
Attributes = Author, Type, Category, Subject
Options Type = Routine, Software Installation, Problem Fixed, Configuration, Other
Options Category = General, Hardware, Software, Network, Other
Extendable Options = Category
Required Attributes = Author
Page Title = ELOG - $subject
Reverse sort = 1
Quick filter = Date, Type

ELOG V3.1.5-fe60aaf