> Ive just installed the RPM of Elog 2.3.2 and ive found a bug relating to 
> port bindings, basically im running elog bound to port 81 and when i 
> install the new RPM it refuses to bind to this port, i tried port 8080 and 
> that worked fine
> 
> Any ideas ?

This is a bug I discovered myself just today, so we are working on it. I 
expect this to be fixed by tomorrow or somewhen during this weekend.

- Stefan

Ive just installed the RPM of Elog 2.3.2 and ive found a bug relating to 
port bindings, basically im running elog bound to port 81 and when i 
install the new RPM it refuses to bind to this port, i tried port 8080 and 
that worked fine

Any ideas ?

Dear Friends,

Anyone managed to compile elog on AIX 5.2 or 5.1 ... is there a binary 
anywhere?

new to "C"

kind regards Aamir

Operator error. Figures!

Elog has worked fine for a log time then I upgraded and added stunnel at the
same time. A case of not seeing the forest for the trees.

Thanks for the help.


> > > I'm using elog 2.3.1 on redhat 7.1 and using stunnel to redirect from port
> > > 443 to 8080. When I try to add a new record (click submit) https:// in the
> > > browser gets changed to http://. I ve tried three browsers all with the 
> same
> > > result. If I go into the address field and change it to https:// after
> > > getting a 404 error it works. The record gets posted.
> 
> This is due to a change we had to do in the redirection of the pages. If you 
> submit a page, the result is a redirection using the HTTP 
> statement "Location: ..." inside the header. While this was a relative link 
> in the previous versions, we changed this into an absolute link, which then 
> agrees with the standard. But since elgod does not know if it runs 
> under "http:" or "https:", you have now to add the line
> 
> URL = https://your.server:port
> 
> into elogd.cfg. I will add this note into the documentation.
> 
> - Stefan

> > I'm using elog 2.3.1 on redhat 7.1 and using stunnel to redirect from port
> > 443 to 8080. When I try to add a new record (click submit) https:// in the
> > browser gets changed to http://. I ve tried three browsers all with the 
same
> > result. If I go into the address field and change it to https:// after
> > getting a 404 error it works. The record gets posted.

This is due to a change we had to do in the redirection of the pages. If you 
submit a page, the result is a redirection using the HTTP 
statement "Location: ..." inside the header. While this was a relative link 
in the previous versions, we changed this into an absolute link, which then 
agrees with the standard. But since elgod does not know if it runs 
under "http:" or "https:", you have now to add the line

URL = https://your.server:port

into elogd.cfg. I will add this note into the documentation.

- Stefan

> I hope this is not something I did. 
> 
> I'm using elog 2.3.1 on redhat 7.1 and using stunnel to redirect from port
> 443 to 8080. When I try to add a new record (click submit) https:// in the
> browser gets changed to http://. I ve tried three browsers all with the same
> result. If I go into the address field and change it to https:// after
> getting a 404 error it works. The record gets posted.

Just an update: It does the same thing when I click the back button

I hope this is not something I did. 

I'm using elog 2.3.1 on redhat 7.1 and using stunnel to redirect from port
443 to 8080. When I try to add a new record (click submit) https:// in the
browser gets changed to http://. I ve tried three browsers all with the same
result. If I go into the address field and change it to https:// after
getting a 404 error it works. The record gets posted.

> Stefan and friends,
> 
> without breaching your own security, could it be possible to see what the 
> elogd.cfg file looks like, also if others would like to post theirs, this 
> would be great in building exmaples etc, obviosly an security related or 
> mail server entries hashed out.
> 
> I am a tad new at this stuff, but eventually would try my hand at getting 
> hold of the source code and compiling on AIX and then intergrating into 
> shell and error reporting. - OK .. a bit in the furture anyway, if someone 
> has already done this please post.
> 
> kind regards Aamir

we do recompile a version with ShellOnsubmit and ShellParam
and it works ! actually only on windows
when all test will be finish we'll send the version to Stefan Ritt


Attributes = By, Type, Categorie, Subject, Dossier, Remarks, email1
....
ShellOnSubmit = c:\test\shellTest\Debug\shellTest.exe
ShellParam = /Params %By %Type %Subject %Dossier %Remarks % 
email1 /quietMode "test test"