Demo Discussion
Forum Config Examples Contributions Vulnerabilities
  Discussion forum about ELOG, Page 700 of 807  Not logged in ELOG logo
 Find |  Login |  Help 
New entries since:Thu Jan 1 01:00:00 1970
 Full | Summary | Threaded | Hide attachments  Show all entries    6455 Entries 
Goto page Previous  1, 2, 3 ... 699, 700, 701 ... 805, 806, 807   Next  
ID Date Icon Authordown Author Email Category OS ELOG Version Subject
  1338   Tue Jul 26 20:51:10 2005 Reply Chris Greengreenc@fnal.govRequestLinux2.6.0bRe: Restrict Top Groups to logged-in users?

Stefan Ritt wrote:

Chris Green wrote:
I'd like to be able to prevent non-logged-in users from seeing what logbooks exist in a top group. Currently it seems that one is only required to log in once one has chosen a logbook. Is this possible?


To protect the logbook selection page, you put the "password file = <file>" into the [global] section or the [global <top group>] section. So "hide" the top group selection page, you put a "show top groups = 0" into the [global] section.


I already had the "password file = <file>" in the [global <top group>] section but I was still able to see the logbooks in that section. Neither moving the password line to [global] nor setting Show Top Groups = 0 helped. Am I doing something wrong?

Thanks,
Chris.
  1339   Tue Jul 26 21:05:26 2005 Reply Chris Greengreenc@fnal.govQuestionLinux2.6.0bRe: New and reply pages don't use Page Title

Stefan Ritt wrote:
So if you have time and fun doing it, you could restructure the documentation page into some separate pages, to give people a better overview. Please send the modified pages back to me and I will include them on the web site.

I'll try to put this together in the next week or two. Thanks for all your help,
Chris.
  1341   Tue Jul 26 21:54:39 2005 Reply Chris Greengreenc@fnal.govRequestLinux2.6.0bRe: Restrict Top Groups to logged-in users?

Stefan Ritt wrote:

If you move the "password file = <file>" entry around, you can get fooled by stored cookies. So after each modification, make sure to delete all cookies in your browser.


This didn't work, but after corresponding with Stefan privately, the following did:

[global]
Show Top Groups = 1

[global top_group]
Protect selection page = 1
Password file = papers.pwd

Thanks again, Stefan.
Chris
  1350   Wed Jul 27 17:30:38 2005 Question Chris Greengreenc@fnal.govQuestionLinux2.6.0b3Email subject garbaged when set?
Hi,

So I'm using the CVS version now since I was hoping this would be fixed. If I set the email subject explicitly, viz:

Use Email Subject = [BooNE-ELOG] New submission to $logbook from $Author

The email I get has:

Subject:
=?ISO-8859-1?B?W0Jvb05FLUVMT0ddIE5ldyBzdWJtaXNzaW9uIHRvIENoYXJnZWQgQ3Vyc
mVudCBQaSBQbHVzIGZyb20gQ2hyaXMgR3JlZW4=?=

... which isn't particularly illuminating.

Advice appreciated.

Thanks,
Chris.
  1351   Wed Jul 27 17:38:25 2005 Question Chris Greengreenc@fnal.gov   Notify email recipient of attachments without including?
Hi,

Our elog is going to be taking some large attachments. I've disabled the attachments from going out in the email, but I'd like email recipients to know that the post has attachments associated with it. Is there a mechanism to do this already, or would it be an enhancement? I'm looking for something like:

Email Notify Attachments = 0 | 1 | 2

Where 0 = no notification,
1 = number only,
2 = list

... independent of whether attachments are included with the email itself.

Thanks,
Chris.
  1376   Fri Aug 5 01:13:13 2005 Reply Chris Greengreenc@fnal.govQuestionLinux2.6.0b3Re: Email subject garbaged when set?

Stefan Ritt wrote:

Chris Green wrote:
The email I get has:

Subject:
=?ISO-8859-1?B?W0Jvb05FLUVMT0ddIE5ldyBzdWJtaXNzaW9uIHRvIENoYXJnZWQgQ3Vyc
mVudCBQaSBQbHVzIGZyb20gQ2hyaXMgR3JlZW4=?=

... which isn't particularly illuminating.


This is the BASE64 encoding of the subject. It was discussed here and I implemented it according to RFC2047. All subjects I receive look fine in Outlook and Thunderbird, but not under Pine, which apparently does not implement the RFC correctly. One could of course put a switch into elog to encode it or not. But as soon as you want to send some non-ASCII characters (like the Norwegian as described in the thread mentioned above) you have a problem. Maybe you can configure your email client correctly to interprete the encoded subject?


Apparently the pine people think they're implementing it correctly. Indeed the default subject, "[ISO-8859-1] New ELOG entry" appears just fine. The one for membership confirmation, and anything set in Use Email Subject, however, is borked as above. Maybe the pine bug is something that can be worked around with something simple (like spaces after the ISO spec, or something? Some things work just fine, as I said.

Thanks,
Chris.
  1377   Fri Aug 5 01:15:23 2005 Reply Chris Greengreenc@fnal.gov   Re: Notify email recipient of attachments without including?

Stefan Ritt wrote:

Chris Green wrote:
Hi,

Our elog is going to be taking some large attachments. I've disabled the attachments from going out in the email, but I'd like email recipients to know that the post has attachments associated with it. Is there a mechanism to do this already, or would it be an enhancement? I'm looking for something like:

Email Notify Attachments = 0 | 1 | 2

Where 0 = no notification,
1 = number only,
2 = list

... independent of whether attachments are included with the email itself.

Thanks,
Chris.


I added Email Format = 64 for only attachment names. So you could set Email Format = 111 to get everything except the full attachments.


Thanks for this. Will verify as soon as someone posts to the (now live) logbook.

Chris.
  1379   Fri Aug 5 02:27:15 2005 Angy Chris Greengreenc@fnal.govBug reportLinux2.6.0-CVSTop Groups, Show Top Groups, password file and Protect Selection page have nasty interaction
Hi,

Just as our ELOG went into production, I tripped over a couple of related (I think) bugs.

First, the easy one: line 21368 of src/elogd.c has a compile warning which looks non-benign. I fixed it in my local copy with:

Index: elogd.c
===================================================================
RCS file: /usr/local/cvsroot/elog/src/elogd.c,v
retrieving revision 1.739
diff -r1.739 elogd.c
21368,21369c21368
< sprintf(str, "?fail=1", user);
< redirect(lbs, str);
---
> redirect(lbs, "?fail=1");

Regardless (ie if I use the original CVS code or the patched version), a hard-to trace problem occurs with my configuration whereby users are denied access after password entry at the logbook selection page (even when details are verifiably correct), and users are dropped through to the next (non-protected) Top Group page. This problem goes away if "Protect Selection Page" is turned off.

A kind of "shadow" of this problem occurs if you create a new logbook from the Change Config File page, whereby after creating the new logbook one is dropped through to the next Top Group's selection page after saving the configuration (and the url has ?fail=1 added to it, althoguh line 21368 above is hardly the only place where this could have occurred).

I think all these things are linked. I'd be grateful if you could review this section of this code for possible causes of these problems. While we can operate for now with non-logged-in users able to see our list of logbooks, that is not something we want for the long term.

Thanks for your help,
Chris.
Goto page Previous  1, 2, 3 ... 699, 700, 701 ... 805, 806, 807   Next  
ELOG V3.1.5-3fb85fa6