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

> 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

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

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

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

Ok, I finally found the problem: Whenever a password has a length which can 
be divided by three (like 6 or 9), the last two characters are completely 
ignored. This problem will be fixed in version 2.3.5. Is has to be noted 
that all existing passwords with the mentioned length have to be re-entered 
after the upgrade from 2.3.4 to 2.3.5. Since one cannot log in with the old 
password on those cases, a "Forgot password?" links has been added to the 
login screen, which can be used to create a new password and send it to the 
registered email address.

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?

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

Is there a way to change the title entry for individual log books, and 
forms ive completely rebranded our system but ut stil says ELOG ENTRIES on 
the summary screen

> Is there a way to change the title entry for individual log books, and 
> forms ive completely rebranded our system but ut stil says ELOG ENTRIES on 
> the summary screen

I changed the default title recently to "ELOG - <logbook>" where <logbook> 
is the name of the current logbook. For the individual messages, the 
title "ELOG" can be changed with the elogd.cfg option "Page title". This 
title can even contain attributes from the logook entry like:

Page title = ELOG - $subject

where $subject gets replaced by the subject of the logbook entry.

> > Is there a way to change the title entry for individual log books, and 
> > forms ive completely rebranded our system but ut stil says ELOG ENTRIES 
on 
> > the summary screen
> 
> I changed the default title recently to "ELOG - <logbook>" where <logbook> 
> is the name of the current logbook. For the individual messages, the 
> title "ELOG" can be changed with the elogd.cfg option "Page title". This 
> title can even contain attributes from the logook entry like:
> 
> Page title = ELOG - $subject
> 
> where $subject gets replaced by the subject of the logbook entry.

I have those attributes already working for example

[global]
Page title = Customer Relational Management System < this sets the selection 
page ok

[Config DB]
Page Title = ABC123 - $Customer Name < this sets the individual log book 
entries title

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

> Basically im running elog on a redhat 8 box with stunnel already installed 
> as part of OpenSSL, on the server i ran the command specified in the 
> instructions
> 
> stunnel -d 443 -r 172.16.24.108:81

I haven't tried `stunnel` with elog, but as far as I read from various
sources, stunnel requires you to create an SSL certificate. In attachment,
you'll find a sample case for stunnel and smtp (port 25) + pop3 (port 110).
Hope this helps.

Reference: http://www.tldp.org/linuxfocus/common/sart/index.html

> I was wondering if you can help me understand the concept and if i am doing 
> something wrong with securing Elog via SSL
> 
> Basically im running elog on a redhat 8 box with stunnel already installed 
> as part of OpenSSL, on the server i ran the command specified in the 
> instructions
> 
> stunnel -d 443 -r 172.16.24.108:81
> 
> This command runs on the server, but when I access https://172.16.24.108/ i 
> get a page cannot be displayed, ive also put the URL = 
> https://172.16.24.108 entry in the elogd.cfg file
> 
> HELP!!!!!!!

Can you access your server locally under http://172.16.24.108:81 ??? If not, 
then you maybe specified the wrong port, so check elogd.cfg and the "-p" flag 
when starting elogd. If you can access it, and cannot access it under 
https://, then something must be wrong with your stunnel configuration. Maybe 
you run already a secure server under port 443? User "netstat -a" to check 
that.

Im not running anything on port 443, one thing I did notice is that when 
stunnel is run and setup, I can run a netstat and nothing is bound to those 
ports, if I do a ps -ef | grep stunnel nothing is running, yet it accepts the 
command initially ?


CONFUSED ????

> > I was wondering if you can help me understand the concept and if i am 
doing 
> > something wrong with securing Elog via SSL
> > 
> > Basically im running elog on a redhat 8 box with stunnel already 
installed 
> > as part of OpenSSL, on the server i ran the command specified in the 
> > instructions
> > 
> > stunnel -d 443 -r 172.16.24.108:81
> > 
> > This command runs on the server, but when I access https://172.16.24.108/ 
i 
> > get a page cannot be displayed, ive also put the URL = 
> > https://172.16.24.108 entry in the elogd.cfg file
> > 
> > HELP!!!!!!!
> 
> Can you access your server locally under http://172.16.24.108:81 ??? If 
not, 
> then you maybe specified the wrong port, so check elogd.cfg and the "-p" 
flag 
> when starting elogd. If you can access it, and cannot access it under 
> https://, then something must be wrong with your stunnel configuration. 
Maybe 
> you run already a secure server under port 443? User "netstat -a" to check 
> that.

Ooops, I destroyed the original post, now how can we fix this :)

After upgrading from 2.3.1 to 2.3.3, elog is not able to load any resources
as stylesheets, images or passwordfiles.

Cannot open file /usr/local/elogdata/logbooks/djeks/password!

oops?

> After upgrading from 2.3.1 to 2.3.3, elog is not able to load any resources
> as stylesheets, images or passwordfiles.
> 
> Cannot open file /usr/local/elogdata/logbooks/djeks/password!

If you installed from the RPM, elogd runs under the user "elog". If you have 
installed a previous version under a different user, it might be that elogd 
does not have read or write access to it. A 

"chown -R elog.elog /usr/local/elogdata"

might help.

- Stefan

> > After upgrading from 2.3.1 to 2.3.3, elog is not able to load any resources
> > as stylesheets, images or passwordfiles.
> > 
> > Cannot open file /usr/local/elogdata/logbooks/djeks/password!
> 
> If you installed from the RPM, elogd runs under the user "elog". If you have 
> installed a previous version under a different user, it might be that elogd 
> does not have read or write access to it. A 
> 
> "chown -R elog.elog /usr/local/elogdata"
> 
> might help.
>
 
It did, a lot, guess I missed that one in the changelog.

Had some trouble with subdir too:
changed it to its full path
restarted elogd
worked

As a test I changed subdir to it's relative path
restarted
It kept working

mmmm, I wonder where that twighlight tune comes from ...

Ive just installed the RPM of Elog 2.3.2 and ive found a bug relating to 
port bindings, basically im running elog bound to port 81 and when i 
install the new RPM it refuses to bind to this port, i tried port 8080 and 
that worked fine

Any ideas ?

> Ive just installed the RPM of Elog 2.3.2 and ive found a bug relating to 
> port bindings, basically im running elog bound to port 81 and when i 
> install the new RPM it refuses to bind to this port, i tried port 8080 and 
> that worked fine
> 
> Any ideas ?

This is a bug I discovered myself just today, so we are working on it. I 
expect this to be fixed by tomorrow or somewhen during this weekend.

- Stefan

> > Ive just installed the RPM of Elog 2.3.2 and ive found a bug relating to 
> > port bindings, basically im running elog bound to port 81 and when i 
> > install the new RPM it refuses to bind to this port, i tried port 8080 
and 
> > that worked fine

The bug has been fixed in V 2.3.3 which has been released today.