Demo Discussion
Forum Config Examples Contributions Vulnerabilities
  Discussion forum about ELOG, Page 222 of 806  Not logged in ELOG logo
ID Date Icon Authordown Author Email Category OS ELOG Version Subject
  1860   Fri Jun 23 12:29:30 2006 Reply Stefan Rittstefan.ritt@psi.chQuestionLinux2.6.1Re: restrict access
Even with your config file (I just changed the URL) I get the correct behaviour:



and after I supply my credentials:



My full elogd.cfg is attached for your reference.

I'm pretty sure that you did not delete your old cookies. Try from another computer. Make sure to have the most recent version of elog. Start the elogd daemon with the "-v" flag and watch the communication. I get for example:
GET / HTTP/1.1
Host: localhost:8080
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.0.4) Gecko/20
060508 Firefox/1.5.0.4
Accept: text/xml,application/xml,application/xhtml+xml,text/html;q=0.9,text/plai
n;q=0.8,image/png,*/*;q=0.5
Accept-Language: en-us,en;q=0.5
Accept-Encoding: gzip,deflate
Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.7
Keep-Alive: 300
Connection: keep-alive
Cookie: urem=1


==== Return ================================
....

As you can see, only the "urem" cookie is present. After I logged in, I get:
Cookie: urem=1; unm=stefan; upwd=Z2suZgFszgg==

These cookies identify you as logged in, so the login screen does not appear any more.
  1862   Fri Jun 23 13:43:03 2006 Reply Stefan Rittstefan.ritt@psi.chQuestionLinux2.6.1Re: restrict access

Gerald Ebberink wrote:
As you can see, I have implemented a temporary fix in the way of allowing only certain hosts access. But where does this Internal error come from.


I only can identify this error if you send me your current ("de-sensified") elogd.cfg.
  1871   Wed Jul 5 12:51:25 2006 Reply Stefan Rittstefan.ritt@psi.chBug reportWindows2.6.1-6Re: Corrupt page link

Arno Teunisse wrote:
Just installed the previous version :
====================================
[C:\Program Files\ELOG]elogd -c elogd.cfg
elogd 2.6.1 built May 24 2006, 08:59:09 revision 1688
Indexing logbooks ... done
Server listening on port 8080 ...

And the problem is gone. !!!!

problem is in version :
==========================
[C:\Program Files\ELOG1]elogd -c elogd.cfg
elogd 2.6.1 built Jun 13 2006, 08:43:21 revision 1691
Indexing logbooks ... done
Server listening on port 8080 ...


Thanks for your detailed information. The hint with the two different revisions heally helped. I fixed that in revision 1695, and made an intermediate release 2.6.1-7. This will fix the problem. Can you please check that this is working?
  1873   Mon Jul 10 11:15:25 2006 Reply Stefan Rittstefan.ritt@psi.chQuestionMac OSX2.6.1Re: Canīt run command "make" in OSX

Gerald Ebberink wrote:
This sounds like something I have not encountered, so I think you'll need to wait for Mr. Ritt to solve this.


No, I can't solve this becaue I have no MAC.

Sorry,

Stefan
  1875   Thu Jul 13 08:11:33 2006 Reply Stefan Rittstefan.ritt@psi.chQuestionLinuxELOG V2.6.Re: Setting Subject for ELog email notification

Alan Stone wrote:
Hi,

I have the following elogd.cfg syntax:

; Email notification
Suppress Email to users = 1
Omit Email To = 1
User Email Subject = $subject
Use Email Heading Edit = $subject
Email Report Notify-CMSROC = alstone@fnal.gov

1) The subject is using some default, instead of capturing the $subject string (as
it does with Reply).


You made a typo. It should be

Use Email Subject = $subject

instead of User Email ...


Alan Stone wrote:
2) I want to control the output header "A new entry...".


You do with with

Use Email Heading = $subject

The option Use Email Heading Edit = $subject is only for entries which are edited (as opposed to new entries). Just read the manual!


Alan Stone wrote:
3) The formatting of email body is awkward. For example, "AuthorAlan Stone"
should have at least a space, and maybe a hyphen or colon, "Author: Alan Stone"


The email is formatted in HTML. Standard email programs like Thunderbird display them properly. If you email client has a problem with it, you can switch to plain text encoding with

Email encoding = 1

Best regards,

Stefan
  1876   Thu Jul 13 15:16:53 2006 Reply Stefan Rittstefan.ritt@psi.chQuestionLinux2.6.1-1681Re: Inserting images via Internet Explorer

Elaine Cristina Franchini dos Anjos wrote:
I observed that there is a difference between IE and others browsers.
When I use "insert image" button in Netscape, for instance,
it creates automatically a tag like
[IMG]elog:1/1[/IMG]
and
includes an attachment in the ELOG entry.

When a try to do the same action in Internet Explorer, only
the attachment is created without the tag
[IMG]elog:1/1[/IMG]
.


This is a problem of the JavaScript implementation of Internet Explorer. After some externsive research I found now a way to convince IE to do the right thing. The fix is contains in SVN revision 1701 and will be released with 2.6.2-2 soon.
  1877   Thu Jul 13 15:25:44 2006 Reply Stefan Rittstefan.ritt@psi.chBug reportWindows2.6.1-1681Re: Elogd.exe crashes on windows

Tim Fowler wrote:
I have elog setup to send emails based on the priority of one of the attributes. When a new entry is created, the emails are sent successfully, however if the entry is edited or if you changed the attribute, elogd.exe will crash with a memory access error.

I have tried this and received the same results on different computers and different versions on Elog down to versions 2/6.0 beta 5. (it works correctly in that version).

The attribute in question is setup something like below:

Attributes = Ticket #, Site, Shift, Type, Area, System Name, Description, Priority, Status, Total Down Time, Last Revision

...(omitted config)

Options Priority = High, Medium, Low

...(omitted config)

Use Email Subject = $Site -- $System Name $Description
Use Email From = testuser@myexample.com

;Send email if priority is set to high
Email Priority High = testuser2@myexample.com

Display Email recipients = 1
Email Format = 14


This problem has now been fixed in version 2.6.2.
  1880   Sat Jul 15 17:58:46 2006 Reply Stefan Rittstefan.ritt@psi.chBug reportLinux2.6.2-1702Re: astonished icon

Elaine Cristina Franchini dos Anjos wrote:
Hi Stefan,

I've been trying to use the astonished icon, but the preview or entry
display shows only a broken image.

I found in the elogd.c at line 5556 :
{"8o", "<img src=\"%sicons/eek.png\">"}

I copied the "astonished.png" to "eek.png" and it worked.

Is it the reason of the problem ? ?)


Actually the C code should be "astonished.png" instead of "eek.png". I changed that in revision 1704. BTW, thanks for the Brazilian translation. Astonished
ELOG V3.1.5-3fb85fa6