ID |
Date |
Icon |
Author |
Author Email |
Category |
OS |
ELOG Version |
Subject |
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 |
231
|
Wed Feb 19 14:48:56 2003 |
| Heiko Scheit | h.scheit@mpi-hd.mpg.de | Comment | | | Re: Participation on development of ELOG | > > We are interested in using your ELOG (which we consider to be a wonderful
> > application) even more. We would like to make a few adaptations in your
> > source code, above all to add some functionality that we are missing.
> >
> > I was wondering if there is a way we could coordinate the development
> > together. For instance, would it be of your interest to receive the code
> > adaptations we do and implement it in your future releases?
>
> Sure, I'm very interested in those and ready to merge it into the main
> development tree.
>
> - Stefan
I think it is very good to include this in elog, but,
since this is also a big security risk (especially if people are
running elogd as root) I would suggest a compile time option to
enable this, like: gcc... -DALLOW_SCRIPT ...
The default should be that it is disabled.
Maybe one should only allow it if the user running elogd is NOT root.
Heiko |
230
|
Wed Feb 19 13:28:17 2003 |
| Tomas Rudolf | tomas@mba.be | Question | | | Email notification | Hi Stefan,
I have a question concerning the Email notification in ELOG.
I have been testing various combinations of the parameters you describe in
your documentation :
Email <attribute> <value> = <list>
Use Email Subject = <string>
Use Email From = <string>
Omit Email To = 0|1
Suppress Email to users = 0|1
And I have encountered a problem using the Email <attribute> <value> =
<list>. While this works fine for me when the <attribute> is of a type
textfield, Options or ROptions, I don't seem to be able to have it working
for the MOptions <attribute> = <list>.
The aim is to have an email notification sent only to selected people
instead of everybody. I was hoping that this would work :
[MyLogBook]
MOptions Message_To = NB,LW,EC,MD,CD,TV,AH,TR,JS
...
...
Suppress Email to users = 1
Email Message_To TR = tomas@mba.be
Email Message_To EC = etienne@mba.be
...
...
Of course, the tricky part is that it is "multiple choice" so any
combination of recipients is possible.
Am I missing something?
Thanx for any ideas how to solve this,
Tomas |
|