ID |
Date |
Icon |
Author |
Author Email |
Category |
OS |
ELOG Version |
Subject |
567
|
Fri Jul 2 15:18:20 2004 |
| Alexandre Camsonne | camsonne@jlab.org | Bug report | Linux | 2.5.2 - 2.5.3 | Re: User/Admin privlege question |
Hi,
I also have this problem, when a non admin user logs in he does not have access to
the config file but if he logs out he can then access the config file as non logged
user.
I also tried to upgrade to version 2.5.3 but running under this version does not ask
for passwords so I reverted to 2.5.2.
Besides these few details, your software is great !
Thank you,
Alexandre
> > For some reason if I define a "login user" that is allowed the configure
> > option he is also allowed to change the configuration file. According to the
> > documentation it seems like this should NOT be the case. Any ideas as to
> > what the problem might be?
>
> Unfortunately I cannot reproduce your problem. This leaves few possibilites:
>
> - any login user CAN change his/her full name, email address etc. but only admin
> users can change ALL OTHERS as well. Admin users should see a "change elogd.cfg"
> button on the config page, whil normal users will not
>
> - are you sure you logged out as admin user and loggin in again as non-admin
> user? Under some circumstances, the browser keeps old cookies which can confuse
> things. Best is if you delete all browser cookies and try again (Tools/Internet
> Options/Delete Cookies in IE).
>
> - Stefan |
644
|
Tue Aug 3 05:31:08 2004 |
| Alexandre Camsonne | camsonne@jlab.org | Bug report | Linux | 2.5.2 - 2. | Re: User/Admin privlege question |
Dear Stefan,
I eventually tried the latest version from the CVS.
And it is odd because like when I tried version 2.5.3, it is like it ignores
the passwd file. I guess I must have a problem in my cfg file.
So I can't really test if 2.5.3 or 2.5.4 have the same problem.
Right now I'm still using 2.5.2 which works fine, if i log out and click on
the logbook tab. I get the page which ask for the username and password. The
thing is I don't get returned to the username/password when I hit log out. I
arrive in the state you can see in the unlogged.jpg.
From here if can go into all the logbooks as long as I don't hit the
logbooks tab and worse I can access to all the config files.
Is there something really badly configured in my config file ? I guess it is
not supposed to work that way.
Thank you,
Alexandre |
649
|
Tue Aug 3 14:51:34 2004 |
| Alexandre Camsonne | camsonne@jlab.org | Bug report | Linux | 2.5.2 - 2. | Re: User/Admin privlege question |
The elogd.cfg is attached in the previous message as attachement 3. Sorry it is a
little bit buried between pictures.
The reason I put the picture of the global elogd.cfg is to show that the not logged
user has access to elogd.cfg which is some kind of trouble...
> I just see your [global] part of elogd.cfg, could you send me the complete file?
>
Hi I tried to remove the cookies and it still did not ask for password under 2.5.4.
Has the password file format changed between 2.5.2 and 2.5.3 ?
> What you also could try is to delete all cookies stored in your browser. The way
> cookies are formed changed between 2.5.2 and 2.5.3, so the system could be
> confused by old cookies.
>
> - Stefan |
654
|
Tue Aug 3 20:14:55 2004 |
| Alexandre Camsonne | camsonne@jlab.org | Bug report | Linux | 2.5.2 - 2. | Re: User/Admin privlege question |
Thank you, I misunderstood how the "Guest menu commands" worked I thought I had to specify
a limited set of commands to actually limit guest users.
Thanks again for your wonderful work on this program too.
Regards,
Alexandre
> Ok, now I see your problem. You defined a "Guest menu commands" which explicitly allows
> not-authorized access (that's what it's for). If you only want to allow authorized
> access, remove the "guest menu commands" from the logbook sections and also from the
> [global] section.
>
> Please note that if an option is not preent in a logbook section, it is looked for in
> the [global] section. I see that most of your logbooks have similar settings. Just put
> them into the [global] section, and override it in the logbook section if they are
> different. |
293
|
Tue Apr 22 17:13:08 2003 |
| Alexander ZVYAGIN | Alexander.Zviagine@cern.ch | Bug report | | | 'Reply' removes attachments from the original message |
It seems when I use "reply" with an attachments, the original attachments of
the message are removed.
I use elog-2.3.5
Alexander. |
295
|
Tue Apr 22 17:17:36 2003 |
| Alexander ZVYAGIN | Alexander.Zviagine@cern.ch | Bug report | | | problem with 20+ attachments |
It seems that maximal number of attachments is about 20. When you try to add
more, a new entry _is_ added to the logbook but the refernce to it is not
added to the web page. |
296
|
Tue Apr 22 17:20:19 2003 |
| Alexander ZVYAGIN | Alexander.Zviagine@cern.ch | Bug report | | | Re: 'Reply' removes attachments from the original message |
> > It seems when I use "reply" with an attachments, the original attachments of
> > the message are removed.
> >
> > I use elog-2.3.5
> >
> > Alexander.
>
> Please see elog:280 . I will releae 2.3.6 with this bugfix somewhen during
> this week.
>
> - Stefan
Wow! Fast reply!!! Thanks a lot! |
298
|
Tue Apr 22 17:34:52 2003 |
| Alexander ZVYAGIN | Alexander.Zviagine@cern.ch | Bug report | | | Re: problem with 20+ attachments |
> > It seems that maximal number of attachments is about 20. When you try to add
> > more, a new entry _is_ added to the logbook but the refernce to it is not
> > added to the web page.
>
> Uhhh, Mr. "monster of number of attachments" gave it's stroke!
:) I wanted to post a message with ~200 attachments.
>Well, we never
> had such large number of attachments so I forgot to put a waring in. The
> limit comes from
>
> #define MAX_ATTACHMENTS 20
>
> in elogd.c which you can easily increase (as long as you have RAM!) and
> recompile.
Actually my report was NOT about this limitation. You have it - it is fine.
The problem is that I add some 'zombies' or dead files to my logbook.
BTW is there a tool to check the 'integrity' of a logbook? That all
attachments are in place, there are no dead files, etc. I perfectly
understand that it is not _highly_ desired or needed, but with the two last
problems (auto-removing of attached files and silent adding a new ones with
20+ attachments) I have doubts that our logbook in a good state. And we just
started to use it. And I am still so excited about it!! |