Demo Discussion
Forum Config Examples Contributions Vulnerabilities
  Discussion forum about ELOG  Not logged in ELOG logo
icon1.gif   restrict access, posted by Gerald Ebberink on Wed Jun 21 22:11:15 2006 
    icon2.gif   Re: restrict access, posted by Stefan Ritt on Thu Jun 22 08:04:13 2006 
       icon2.gif   Re: restrict access, posted by Gerald Ebberink on Thu Jun 22 11:29:17 2006 
          icon2.gif   Re: restrict access, posted by Stefan Ritt on Thu Jun 22 11:38:38 2006 
             icon2.gif   Re: restrict access, posted by Gerald Ebberink on Thu Jun 22 12:10:00 2006 
                icon2.gif   Re: restrict access, posted by Stefan Ritt on Fri Jun 23 12:29:30 2006 elogd.cfgCapture.jpgCapture.jpg
                   icon2.gif   Re: restrict access, posted by Gerald Ebberink on Fri Jun 23 13:16:57 2006 
                      icon2.gif   Re: restrict access, posted by Stefan Ritt on Fri Jun 23 13:43:03 2006 
                         icon2.gif   Re: restrict access, posted by Gerald Ebberink on Fri Jun 23 14:57:02 2006 elog.conf
                         icon2.gif   Re: restrict access, posted by Gerald Ebberink on Mon Jul 17 13:20:07 2006 
Message ID: 1861     Entry time: Fri Jun 23 13:16:57 2006     In reply to: 1860     Reply to this: 1862
Icon: Reply  Author: Gerald Ebberink  Author Email: g.h.p.ebberink@nclr.nl 
Category: Question  OS: Linux  ELOG Version: 2.6.1 
Subject: Re: restrict access 
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:

Well actualy these old cookies don't exist, but I found an error in the verbose mode.
GET / HTTP/1.1
Host: hostname
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8.0.4) Gecko/20060608 Ubuntu/dapper-security Firefox/1.5.0.4
Accept: text/xml,application/xml,application/xhtml+xml,text/html;q=0.9,text/plain;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=0


Remote host "hostname" matches "ALL" in "Hosts deny". Access denied.
Remote host "hostname" matches "hostname" in "Hosts allow". Access granted.
Internal error, no valid header!

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 use the standard packaged version of elog (V2.6.1) from the Ubuntu repositories.
ELOG V3.1.5-3fb85fa6