|
|
|
Demo
Discussion
|
|
Forum
Config Examples
Contributions
Vulnerabilities
|
| Discussion forum about ELOG, Page 168 of 807 |
Not logged in |
 |
|
|
|
|
Re: restrict access, posted by Stefan Ritt on Fri Jun 23 12:29:30 2006 
|
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. |
|
Re: restrict access, posted by Gerald Ebberink on Fri Jun 23 13:16:57 2006
|
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. |
|
Re: restrict access, posted by Stefan Ritt on Fri Jun 23 13:43:03 2006
|
| 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. |
|
Re: restrict access, posted by Gerald Ebberink on Fri Jun 23 14:57:02 2006
|
| I only can identify this error if you send me your current ("de-sensified") elogd.cfg. |
Here you are.. |
|
Re: Canīt run command "make" in OSX, posted by Steve Jones on Tue Jul 4 07:04:19 2006
|
| Mats McLund wrote: | Hello.
I think to test Elog in Mac G5 with OSX 10.4.6.
In the manual is following installationtext:
"Installation from the tarball:
Download the latest elog-x.x.x.tar.gz package.
Expand the compressed TAR file with tar -xzvf elog-x.x.x.tar.gz. This creates a subdirectory elog-x.x.x where x.x.x is the version number. In that directory execute make, which creates the executables elogd, elog and elconv."
The problem is when i try to run the command "make" in ~/elog-2.6.1 subdirectory. I get following message:
-bash: make: command not found
Now, Im not an "UNIX-hacker" so I will be glad if anyone maybe can help me?
Best regardīs
Mats McLund |
| Quote: | | Typically one would install the Gnu compiler series and with that come 'gmake'. Barring that, and not knowing anything about OSx, if OSx comes with its own compiler series then make might be somewhere on the system but not in your path. Go to http://gcc.gnu.org/ and see if you an find a pre-built version of gcc -- all I found mentioned "darwin". Perhaps Apple has something in the way of a development colleciton? |
|
|
Re: Canīt run command "make" in OSX, posted by Mats McLund on Tue Jul 4 08:46:15 2006
|
| Steve Jones wrote: |
| Mats McLund wrote: | Hello.
I think to test Elog in Mac G5 with OSX 10.4.6.
In the manual is following installationtext:
"Installation from the tarball:
Download the latest elog-x.x.x.tar.gz package.
Expand the compressed TAR file with tar -xzvf elog-x.x.x.tar.gz. This creates a subdirectory elog-x.x.x where x.x.x is the version number. In that directory execute make, which creates the executables elogd, elog and elconv."
The problem is when i try to run the command "make" in ~/elog-2.6.1 subdirectory. I get following message:
-bash: make: command not found
Now, Im not an "UNIX-hacker" so I will be glad if anyone maybe can help me?
Best regardīs
Mats McLund |
| Quote: | | Typically one would install the Gnu compiler series and with that come 'gmake'. Barring that, and not knowing anything about OSx, if OSx comes with its own compiler series then make might be somewhere on the system but not in your path. Go to http://gcc.gnu.org/ and see if you an find a pre-built version of gcc -- all I found mentioned "darwin". Perhaps Apple has something in the way of a development colleciton? |
|
Hi Steve.
I have now found a compiler on Apples Developer Tools --- they came as a CD from Apple with my Mac G5.
Great thanks to mr Thomas R. Vilberg for that tips!
I have now the "make"-commands to work as you see.
McLunds-G5:~/elog-2.6.1 admin$ ls -al
total 3984
drwxr-xr-x 21 1093 110 714 Jun 30 14:55 .
drwxrwxr-x 45 admin staff 1530 Jun 30 14:52 ..
-rwxr-xr-x 1 1093 110 17982 Oct 7 2005 COPYING
-rw-r--r-- 1 1093 110 3702 Mar 6 20:32 Makefile
-rw-r--r-- 1 1093 110 327 Oct 7 2005 README
drwxr-xr-x 11 1093 110 374 Apr 1 15:29 contrib
drwxr-xr-x 19 1093 110 646 Apr 1 15:29 doc
-rwxr-xr-x 1 root 110 35020 Jun 30 14:55 elconv
-rwxr-xr-x 1 root 110 43152 Jun 30 14:53 elog
-rwxr-xr-x 1 root 110 1806608 Jun 30 14:54 elogd
-rwxr-xr-x 1 1093 110 412 Mar 28 17:19 elogd.cfg
-rwxr-xr-x 1 1093 110 1256 Jan 19 09:19 elogd.init_template
drwxr-xr-x 3 1093 110 102 Apr 1 15:29 logbooks
drwxr-xr-x 5 1093 110 170 Apr 1 15:29 man
-rw-r--r-- 1 root 110 56868 Jun 30 14:53 mxml.o
-rw-r--r-- 1 root 110 46844 Jun 30 14:53 regex.o
drwxr-xr-x 31 1093 110 1054 Apr 1 15:29 resources
drwxr-xr-x 3 1093 110 102 Apr 1 15:29 scripts
drwxr-xr-x 8 1093 110 272 Apr 1 15:29 src
-rw-r--r-- 1 root 110 1672 Jun 30 14:53 strlcpy.o
drwxr-xr-x 3 1093 110 102 Apr 1 15:29 themes
But....
When I try to run "elogd -p 8080" or just "elogd" after installation I get message "-bash: elogd: command not found" 
You maybe have some other trick to start elogd?
Best regards and thanks for all help.
Mats McLund |
|
Re: Canīt run command "make" in OSX, posted by Gerald Ebberink on Tue Jul 4 08:52:47 2006
|
| Mats McLund wrote: |
But....
When I try to run "elogd -p 8080" or just "elogd" after installation I get message "-bash: elogd: command not found"
You maybe have some other trick to start elogd?
Best regards and thanks for all help.
Mats McLund |
Mats,
What you might want to try is the following (it works for linux which has bash)
in the elog directory run "./elogd -p 8080" you see the dot slash in there that means it should run the file in the local directory.
of that works you could try run "make install" in which case it will be installed in the directory where it can be found as a command.
these are just my 2 cents. |
|
Re: Canīt run command "make" in OSX, posted by Mats McLund on Tue Jul 4 13:07:53 2006
|
| Gerald Ebberink wrote: |
| Mats McLund wrote: |
But....
When I try to run "elogd -p 8080" or just "elogd" after installation I get message "-bash: elogd: command not found"
You maybe have some other trick to start elogd?
Best regards and thanks for all help.
Mats McLund |
Mats,
What you might want to try is the following (it works for linux which has bash)
in the elog directory run "./elogd -p 8080" you see the dot slash in there that means it should run the file in the local directory.
of that works you could try run "make install" in which case it will be installed in the directory where it can be found as a command.
these are just my 2 cents. |
Hello Gerald.
Tank you for your help!
But.....
When I run ./elogd -p 8080 I get "Bus error" message.
Best regards
Mats McLund |