Hello, This is coming up as a high vulnerability in our scans. Are there plans to update the rpm for this fix? If so is there an ETA? Any update would be much appreciated. Currently running elog-3.1.4-2 

Thank you for your work. Works like a charm!

Running elog-3.1.4-3 Can't add users through the web interface. Clicking add user and writing all the fields in with something doesn't add a user into the PWD file of that logbook. Running a tail -f on the password file shows elog writes the user info with the hashed password 3 times and then deletes the information about 20 seconds later. Has anyone else had a similar issue? This is running on RHEL8.3

Currently have multiple logbooks hosted with elogd. One book is having an issue with Categories. The user regulary uses the category filtering to see one subject for the whole month. This past week it hasn't been working properly. When choosing a drop down category to filter there are not logs found. I've notice the fields under the categories change randomly. Sometimes it would add a % sign where there should be --. Some other fields go from displaying -- Subject -- to just the dashes, thats when the filtered eLogs do not show. Clearing out the erroneous characters can eventually load the specified logs. Has anyone else seen this? Should I just upgrade the system and hope for the best?

PS. while writing this I was able to mitigate the issue by removing the troubled fields from the quick filter section. I'm pretty sure this will not be an issue for my end user but any input is appreciated.

Dear all,

I am trying to get elog used in our company but I need some help.
I have two small questions:

-1- how can I restrict the access 
of a certain user such that he can only see certain logbooks. 
But also not showing the other logbooks on the selection page.
So we could have a tree like this:

Stage one
|
|->Stage 2
       |
       |
      / \
     |   |
    Co1 Co2
    /     \
  job     job

So when Co1 logs in the should not be able to see Co2 and the attached job

-2- How can I have a login page instead of the logbook selection page.
When I insert the password statement the config, I get a blank page.

> > -1- how can I restrict the access 
> > of a certain user such that he can only see certain logbooks. 
> 
> This can be achieved with the "Login user = ..." option.

That is what I found in the mean time. And it works like a charm.

> 
> > But also not showing the other logbooks on the selection page.
> 
> You could try to use "top groups". This gives you "separate" groups of logbooks, so you could make a public tree
> seen by everybody and private trees only seen by a few people. Please read the documentation for details.

I'm now using this (I had to redesign our tree for that)

> > -2- How can I have a login page instead of the logbook selection page.
> > When I insert the password statement the config, I get a blank page.
> 
> You get a login page instead of the selection page if the "Password file = " statement is in the [global] section
> and "Protect selection page = 1". You might have to delete all cookies in your browser if you move the password
> file statement between the [global] and the logbook sections, because otherwise the old cookies might prevent you
> from logging out.

This is not working for me, in Mozilla Firefox I'm still getting a blank page, where IE is giving me an error
stating
that the page is unavailable