Demo Discussion
Forum Config Examples Contributions Vulnerabilities
  Discussion forum about ELOG, Page 132 of 807  Not logged in ELOG logo
 Find |  Login |  Help 
 Full | Summary | Threaded | Show attachments  Show only new entries    6451 Entries 
Goto page Previous  1, 2, 3 ... 131, 132, 133 ... 805, 806, 807   Next  
ID Date Icon Author Author Email Category OS ELOG Version Subjectdown
  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.
  1861   Fri Jun 23 13:16:57 2006 Reply Gerald Ebberinkg.h.p.ebberink@nclr.nlQuestionLinux2.6.1Re: 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.
  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.
  1863   Fri Jun 23 14:57:02 2006 Reply Gerald Ebberinkg.h.p.ebberink@nclr.nlQuestionLinux2.6.1Re: restrict access
I only can identify this error if you send me your current ("de-sensified") elogd.cfg.


Here you are..
  1881   Mon Jul 17 13:20:07 2006 Reply Gerald Ebberinkg.h.p.ebberink@nclr.nlQuestionLinux2.6.1Re: restrict access

Stefan Ritt wrote:

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.


I have just installed the svn version of elog, and the problem has been fixed.

Thank you very much!
  66172   Mon Jan 26 19:48:42 2009 Reply Stefan Rittstefan.ritt@psi.chQuestionLinux2.7.4Re: restrict a field to upper or lower case

 

lisa giaime wrote:

Is it possiblet to restrict a field so that when a new record is added, whatever the user types is automatically converted to lower case?

 

No, this is not possible. 

  68191   Tue Nov 17 08:33:15 2015 Reply Stefan Rittstefan.ritt@psi.chQuestionLinux3.1.0Re: resending information confirmation box after refresh interval

Start with the demo example configuration, add one line after the other from your config, and figure out which is the offending statement in your config, then post a minimal configuration here which triggers the problem.

Ken Ludington wrote:

After submitting a new post, if the page is left completely alone,, it will after a few minutes prompt that the page needs to resend information.

This is the same prompt you'd get if you attempt to refresh a page that had session variables passsed to it. Example is attached.

Is there something in my config that could cause this?   This is a fresh install of the latest verison however my elogd.cfg file has been migrated throuh many installs over many versions, so it's very possible this is something following along.

thanks.

 

  1751   Mon Mar 6 13:50:07 2006 Reply Stefan Rittstefan.ritt@psi.chRequestAll2.6.1-1668Re: require smileys to have whitespace on either side?

Glenn Horton-Smith wrote:
It would be nice if elog would only interpret something as a smiley if it is surrounded by whitespace. It can be particularly annoying that an 8 followed by a right paren becomes a "cool" smiley -- e.g., a parenthetical reference to event eighteen (18) becomes mangled... [That was "18" inside the parens.]

Is there already a way to solve this issue (other than always previewing your entries and adding spaces before parans)? Is the feature hard to implement?


Interpreting smileys only if they are surrounded by whitespace does not solve the problem completely. It will solve it for (1\8), but not if you have (1, \8) (1, 9) in your text. So it's not a good solution. If you have problems with simleys, I would post my text in plain mode, or surround your numbers with [code]...[/code] tags. If you write

[code](1\8)[/code]

then it will look like
(18)

which should be fine.
Goto page Previous  1, 2, 3 ... 131, 132, 133 ... 805, 806, 807   Next  
ELOG V3.1.5-3fb85fa6