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.

> 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

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

> Is there a way to hide logbooks from all views.
> 
> Basically i want to use the move function to move old entries to another 
> logbook but only want administrators to be able to see the logbooks in the 
> view, everyone will just see the primary ones.
> 
> At the min im having to put Archive logbook, everyone is complaining at me 
> that there is too many to choose from :)
> 
> Any suggestions ?

What about grouping the archive logbooks into a logbook group? Like:

Group Pubilc = Logook1, Logbook2, ...
Group Archive = Archive1, Archive2, ...

So if a "normal" user is in the public group, it only sees Logoook1, ... and 
a single tab "archive", which is then (I hope) not too much to choose from.