ID |
Date |
Icon |
Author |
Author Email |
Category |
OS |
ELOG Version |
Subject |
239
|
Wed Feb 26 10:34:12 2003 |
| Stefan Ritt | stefan.ritt@psi.ch | Comment | | | Re: Security (passwords over web browser) | > Stefan - Just to say that this is an excellent piece of work well done.
Thanks.
> 1) is there a way around seeing the password in text when self
regestering,
> if I turn this option off when the user changes his password will this
> password still be seen?
Where did you see the password? Was it on this logbook or on your own? Did
you use "self register" equal 3 or 2? The password should never be visible
in plain text, so after you submit it (during registration or login), the
page gets immediately redirected since the password is contained in the
URL. After the redirection, it is not visible any more. Now it might happen
that the redirection takes a few seconds, depending on the network speed,
then you see it for this few seconds. But in an intranet installation, this
should not happen.
> 2) I have changed all the files to be owned on my RedHat Server by the
> user:group as elog:elog and set and moved the logbooks to another
directory
> other than in /usr/local/elog namely /home/elog/logbooks, my concern is
is
> I was to upgrade to a newer version would it be a simple install over the
> top? any caveats?
Yes, if you upgrade, the new version will again to into /usr/local/elog
unless you tell "rpm" to relocate the package. Unfortunately I'm not a
specialist with "rpm", but you might figure it out yourself (just try to
reinstall the same version and look where the files go wiht "rpm -ql elog"). |
238
|
Wed Feb 26 10:13:10 2003 |
| Stefan Ritt | stefan.ritt@psi.ch | Request | | | Re: elogd.cfg | > Stefan and friends,
>
> without breaching your own security, could it be possible to see what the
> elogd.cfg file looks like, also if others would like to post theirs, this
> would be great in building exmaples etc, obviosly an security related or
> mail server entries hashed out.
Ok, good idea. I made a new logbook "Config Examples" on this server, where
everybody can add new configuration examples. I added a few covering the
logbooks on this server as a starting point. Just click on "Config Examples"
at the top of this page! |
237
|
Tue Feb 25 22:35:44 2003 |
| Aamir Khan | aamir@aamir.uk.com | Request | | | elogd.cfg | Stefan and friends,
without breaching your own security, could it be possible to see what the
elogd.cfg file looks like, also if others would like to post theirs, this
would be great in building exmaples etc, obviosly an security related or
mail server entries hashed out.
I am a tad new at this stuff, but eventually would try my hand at getting
hold of the source code and compiling on AIX and then intergrating into
shell and error reporting. - OK .. a bit in the furture anyway, if someone
has already done this please post.
kind regards Aamir |
236
|
Tue Feb 25 22:18:57 2003 |
| Aamir Khan | aamir@aamir.uk.com | Comment | | | Security (passwords over web browser) | Stefan - Just to say that this is an excellent piece of work well done.
I have just started an internal company Elog server, couple of
clarifications :
1) is there a way around seeing the password in text when self regestering,
if I turn this option off when the user changes his password will this
password still be seen?
2) I have changed all the files to be owned on my RedHat Server by the
user:group as elog:elog and set and moved the logbooks to another directory
other than in /usr/local/elog namely /home/elog/logbooks, my concern is is
I was to upgrade to a newer version would it be a simple install over the
top? any caveats?
thanks again an absolute dream program.
kind regards Aamir |
235
|
Mon Feb 24 14:40:30 2003 |
| Stefan Ritt | stefan.ritt@psi.ch | Question | | | Re: Email notification | This problem has been fixed as well (elog:233). |
234
|
Mon Feb 24 13:22:06 2003 |
| Stefan Ritt | stefan.ritt@psi.ch | Bug report | | | Re: Themes BUG ? | > Is the DEFAULT theme somehow hardcoded for the login screen and the main
> menu ?
Yes, this was in and certainly is not correct. So I fixed it, the new code
can be obtained vom CVS (see elog:233). |
233
|
Mon Feb 24 13:20:19 2003 |
| Stefan Ritt | stefan.ritt@psi.ch | | | | ELOG source code from CVS | To obtain the newest source code of ELOG, go to the CVS repository at
http://midas.psi.ch/cgi-bin/cvsweb/elog/src
It contains usually the newest bug fixes, which will show up in the next
realease. On the other hand it can also contain some new features, which
are not yet fully tested, so care should be taken when using it. The
revision comments usually explain what is new in that revision. |
232
|
Mon Feb 24 09:23:39 2003 |
| Tomas Rudolf | tomas@mba.be | Bug report | | | Themes BUG ? | Hi,
We prepared a customized theme to use with ELOG. It's called for example
my_theme and is situated in the THEMES directory (together with the DEFAULT
theme).
I defined the my_theme the global theme for ELOG:
[global]
Theme = my_theme
And it works fine for all the logbook in ELOG. However. The login screen
and the main menu screen (the one with list of logbooks and # of entries)
still takes the DEFAULT theme.
If I change the my_theme name to default then everything works correctly
(logon + main menu + all logbooks have the desired look).
Is the DEFAULT theme somehow hardcoded for the login screen and the main
menu ?
Thanx for your answer
Tomas Rudolf |
|