A problem (elog:272) with certain passwords has been fixed in version 
2.3.5 of ELOG. This forum runs the updated version, which can cause login 
problems. All users with a password length of 3,6,9,12,... characters 
cannot login with their old password anymore. They have to click 
on "Forgot password?" in the login screen to have the system create a new 
password for them and send it to their registered email address. In case 
no email address has been registered, one can send me directly an email 
(stefan.ritt@psi.ch). After one receives the new password via 
email, one can log in again and change the password to the old one, which 
then gets registered correctly. I apologize for any inconvenience.

- Stefan

> 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.

This Forum runs on "midas.psi.ch" under RH 7.1, Apache 1.3.22, port 8000, and 
it contains in httpd.conf:

Redirect permanent /elogdemo http://midas.psi.ch/elogdemo/
ProxyPass /elogdemo/ http://midas.psi.ch:8000/

elogd.cfg contains:

URL = http://midas.psi.ch/elogdemo/

As you can see, it works fine with all browsers, so I have no clue what is 
wrong in your case. You might want to look at your /var/log/httpd/access_log 
and /var/log/httpd/error_log to see what's going on. If you run elogd 
interactively with the "-v" flag, you see directly the communication between 
elogd and the browser which also might help.

- Stefan

Forgot password option generates an error message

Password file hashes are different causing migrated password files to fail 
but only for certain users, try password 516135 hashed in 2.3.4 and compare 
to version 2.3.5 they are different.

Summary page title = string doesnt work also it results in the default ELOG 
DB Name

HELP

> Forgot password option generates an error message

Which error? Can you be more specific. I tried it myself with this forum and 
it worked for me.

> Password file hashes are different causing migrated password files to fail 
> but only for certain users, try password 516135 hashed in 2.3.4 and compare 
> to version 2.3.5 they are different.

Yes indeed. Please see elog:273 for more details

> Summary page title = string doesnt work also it results in the default ELOG 
> DB Name

Thanks, has just been fixed, new version under CVS.

- Stefan

> > Forgot password option generates an error message
> 
> Which error? Can you be more specific. I tried it myself with this forum 
and 
> it worked for me.

Error sending Email 
Please use your browser's back button to go back  

HTTP/1.1 200 Document follows Server: ELOG HTTP 2.3.5 Content-Type: 
text/html;charset=iso-8859-1 Connection: Keep-Alive Keep-Alive: timeout=60, 
max=10 
User name "nickc" not registered 
Please use your browser's back button to go back  

Yet nickc is in the password file, it generates the same message for any 
other users in there too.


> 
> > Password file hashes are different causing migrated password files to 
fail 
> > but only for certain users, try password 516135 hashed in 2.3.4 and 
compare 
> > to version 2.3.5 they are different.
> 
> Yes indeed. Please see elog:273 for more details

Is there a way to convert all the hashes from one system to another, the 
problem ive got is my password files are quiet large and want upgrades of 
this nature to go seemlessly without people complaining about it.

> 
> > Summary page title = string doesnt work also it results in the default 
ELOG 
> > DB Name
> 
> Thanks, has just been fixed, new version under CVS.
> 
> - Stefan
Ta

> Error sending Email 
> Please use your browser's back button to go back  

This error is caused if elogd cannot contact your SMTP server for sending 
email. Can you please check the "SMTP host" entry in the configuration file?

> Is there a way to convert all the hashes from one system to another, the 
> problem ive got is my password files are quiet large and want upgrades of 
> this nature to go seemlessly without people complaining about it.

Unfortunately not. The old system had a bug which deleted the last one or two 
characters, if the password length was dividable by three. Since the 
characters were deleted, there is no way to reconstruct the full password. I 
apoligize for the inconveniences, I know that this can cause lot of trouble, 
but therefore I implemented the "Forgot password?" functionality, so that 
users can log in again. Alternatively, one can edit the password file, delete 
all passwords, and ask the users to log in without password and change it 
afterwards immediately.

I am using 2.3.4 and I am still having this problem.  If someone posts a
message with an attachment, and I then reply to that message, the attachment
gets 'deattached' from that message.  However, the file is still in the
logbook directory, so it is possible to recover it, but it did cause a slight
panic the first time it happened :)

I see there is a 2.3.5 version now, but the changelog doesn't say anything
about this problem, so I have not tried it yet.

Is there a 'trick' to fix this problem?

EDIT: I noticed when I replyed to your message, your elog.cfg attachment is
no longer there.  So it appears it's not fixed in 2.3.5 either..


> This is a known problem and has been fixed in version 2.3.4, which has been 
> released today. To prove that it's working, I attached the current 
> elogd.cfg from this forum.

> I am using 2.3.4 and I am still having this problem.  If someone posts a
> message with an attachment, and I then reply to that message, the attachment
> gets 'deattached' from that message.  However, the file is still in the
> logbook directory, so it is possible to recover it, but it did cause a 
slight
> panic the first time it happened :)

Uups, that is indeed a problem. I found that it was unrelated to the first 
one, so it was there since quite some time now. I fixed it. It will come out 
in 2.3.6 or can be obtained already now from CVS. It is trongly recommended 
to upgrade all installations to avoid this problem.