Demo Discussion
Forum Config Examples Contributions Vulnerabilities
  Discussion forum about ELOG  Not logged in ELOG logo
icon1.gif   (my) Firefox breaks Elog with this config file, posted by Michael Husbyn on Wed Jun 24 13:23:49 2009 elogd.cfg
    icon2.gif   Re: (my) Firefox breaks Elog with this config file, posted by Stefan Ritt on Wed Jun 24 14:28:43 2009 
       icon2.gif   Re: (my) Firefox breaks Elog with this config file, posted by Michael Husbyn on Thu Jun 25 09:07:51 2009 
          icon2.gif   Re: (my) Firefox breaks Elog with this config file, posted by Stefan Ritt on Thu Jun 25 09:26:00 2009 
             icon2.gif   Re: (my) Firefox breaks Elog with this config file, posted by Michael Husbyn on Thu Jun 25 10:21:10 2009 
                icon2.gif   Re: (my) Firefox breaks Elog with this config file, posted by Stefan Ritt on Thu Jun 25 10:51:12 2009 
                   icon2.gif   Re: (my) Firefox breaks Elog with this config file, posted by Michael Husbyn on Thu Jun 25 11:04:53 2009 
Message ID: 66410     Entry time: Wed Jun 24 14:28:43 2009     In reply to: 66409     Reply to this: 66412
Icon: Reply  Author: Stefan Ritt  Author Email: stefan.ritt@psi.ch 
Category: Bug report  OS: Windows  ELOG Version: 2.7.6 
Subject: Re: (my) Firefox breaks Elog with this config file 

Michael Husbyn wrote:
Hi, Did a fresh install on a Windows 2003 server (and tried it on my personal computer) After startup I can click on Norway/nor, and then the server just stops responding. I see in the log nothing, the last line: Received unknown cooke "style" Then it stops responding and after a few seconds I see the dos window returns to commandline prompt. Probably a very bad config file. On Windows XP it informs we of Dr Watson, memory could not be read message. Using Firefox 3.0.11 But if I use IE 7, no problem at all.. Any suggestion? Best regards Michael Husbyn

This must be related to the unknown cookie "style". There was some work recently on elog to make it robust against unknonw cookies. The latest modification was on version 2192, and you probably have an older version. I made a release elog276-2.exe for you. Try it and let me know. You can also just delete your cookies in Firefor and it should be fine, but it's better not being able to crash elog. 

ELOG V3.1.5-fe60aaf