> I need something to set the title of the page when on the summary page for 
> the logbook, as it just says ELOG - Config DB (this isnt set anywhere)

I added the option "Summary page title = xxx" in a similar way than the "Page 
title". The new version is at

http://midas.psi.ch/cgi-bin/cvsweb/elog/src/elogd.c?rev=1.64

It will be included in the release 2.3.5 of elog.

- Stefan

When I use the <Login user => option to specify what users I want to be 
able to login into the different logbooks it does not seem to work.  Is 
there something else you are supposed to do to restrict what logbooks users 
can log into?

I noticed that when I put in a password such as <test1> a person can login 
with the password <test2> or any other number at the end.  Is the 
encryption not able to tell the difference between numbers?  The encrypted 
passwords even look the same in the password file.  Is this a bug?

> I noticed that when I put in a password such as <test1> a person can login 
> with the password <test2> or any other number at the end.  Is the 
> encryption not able to tell the difference between numbers?  The encrypted 
> passwords even look the same in the password file.  Is this a bug?

This is really strange. Encryption only works on ASCII characters and does 
not distinguish between letters and digits. When I try to reporoduce that, 
the system distinguishes well between "test1" and "test2". The first gives 
encrypted "dGVzdDE=" and the second gives "dGVzdDI=", note the different "E" 
and "I". So I have no clue right now what is wrong in your installation. If 
running under Linux, you can compile elogd after adding "-DHAVE_CRYPT" and "-
lcrypt" to the Makefile to use the standard Linux crypt() function, but I 
would rather like to understand what is wrong in your case.

- Stefan

> When I use the <Login user => option to specify what users I want to be 
> able to login into the different logbooks it does not seem to work.  Is 
> there something else you are supposed to do to restrict what logbooks users 
> can log into?

First, you need version 2.3.4 or later, second, you need a "password file = 
xxx" entry in your elogd.cfg to turn on user-level password access. If both 
is true and you still don't succeed, send me your elogd.cfg.

- Stefan

> > When I use the <Login user => option to specify what users I want to be 
> > able to login into the different logbooks it does not seem to work.  Is 
> > there something else you are supposed to do to restrict what logbooks 
users 
> > can log into?
> 
> First, you need version 2.3.4 or later, second, you need a "password file = 
> xxx" entry in your elogd.cfg to turn on user-level password access. If both 
> is true and you still don't succeed, send me your elogd.cfg.
> 
> - Stefan

Ok, I installed the latest version and this is fixed.  Thanx!

> > I noticed that when I put in a password such as <test1> a person can 
login 
> > with the password <test2> or any other number at the end.  Is the 
> > encryption not able to tell the difference between numbers?  The 
encrypted 
> > passwords even look the same in the password file.  Is this a bug?
> 
> This is really strange. Encryption only works on ASCII characters and does 
> not distinguish between letters and digits. When I try to reporoduce that, 
> the system distinguishes well between "test1" and "test2". The first gives 
> encrypted "dGVzdDE=" and the second gives "dGVzdDI=", note the 
different "E" 
> and "I". So I have no clue right now what is wrong in your installation. If 
> running under Linux, you can compile elogd after adding "-DHAVE_CRYPT" 
and "-
> lcrypt" to the Makefile to use the standard Linux crypt() function, but I 
> would rather like to understand what is wrong in your case.
> 
> - Stefan

Ok, try it with the passwords <hello1> and <hello2>.  Then when you go to log 
in, put in the password of <hello> with any single number after it and let me 
know if the problem shows up for you because that is the password I was 
using.  When I look at it encrypted in the passwd file they look the same.  I 
also installed the latest version today which is newer than the one I was 
using before and it still does it.  I appreciate your time.

Byron

Hi,

I am new to elog so please bear with me if this sounds like a stupid
question... 

I would like to run elogd under Apache because I don't want to open another
port (eg. 8080) on the firewall for incoming http traffic. I followed the
special instructions for that sort of setup but the user logon screen always
comes up again, even after using a valid username/password.

I am testing on a Redhat 7.2 based distribution (called SME server) in a
test domain (tuxhome.co.nz). 
"Apache modules mod_proxy.c and mod_alias.c are activated", Yes.
There seems to be a problem here with the Apache Redirect statement. When I
try with
Redirect permanent /elog http://www.tuxhome.co.nz/elog/
ProxyPass /elog/ http://www.tuxhome.co.nz:8080/
Mozilla responds "Redirection limit for this URL exceeded" and IE6 says
"cannot find server or DNS error" so I have commented out the redirect
statement for now.
I might misunderstand the required URL statement in elogd.cfg 
"URL = http://your.proxy.host/subdir/" ?
which I understand it would have to be 
URL = http://www.tuxhome.co.nz/elog/ for my above example?

Maybe someone could help me with an example that includes all 3 of the
statements together, the redirect + proxypass from httpd.conf plus the URL
from elogd.conf?
Thanks for any help.

Michael