> > i am trying to implement ssl features on our logbooks. however, it seems
> > that stunnel has drastically changed their program and the usual startup
> > procedures listed on the elog page don't work.
> > so, what is the new method for getting elog set up with stunnel?
> 
> stunnel is kind of a deprecated feature. Better use the SSL proxy of Apache,
> as written in the elog admin guide. If someone else figures out how to use the
> more revent stunnel, I'm willing to update the documentation.


okay. that's good to know. i'll try using the apache method instead. but, there is
something wrong with the "secure" link to an example on the elog administrator's
guide.

is there a way to set up a logbook so that a password is required to get
into it, but no username?

is there a way to set up a logbook so that a password is required to get
into it, but no username?

> i

> is there a way to set up a logbook so that a password is required to get
> into it, but no username?

Have a look under "Access control" in the manual. What you need is "Read
Password".

> > is there a way to set up a logbook so that a password is required to get
> > into it, but no username?
> 
> Have a look under "Access control" in the manual. What you need is "Read
> Password".

thanks. that seems to get me the functionality i needed. is there any way to
get rid of the username line when using the "Read Password" feature? as it is
now, you can either leave it blank or enter anything you want, so long as you
use the correct password it still works. however, to keep users from getting
confused, i think it would be better to only have a box asking you for the
password and not both the password and username.

> thanks. that seems to get me the functionality i needed. is there any way to
> get rid of the username line when using the "Read Password" feature?

No, this is an HTTP standard. The dialog box is generated by your browser, and I
do not know any way to prevent it.

there is a guide on the contributions logbook at

elog:Contributions/11

for securing Elog using SSL and Apache.