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"


 

> Stefan - Just to say that this is an excellent piece of work well done.

Thanks.
 
> 1) is there a way around seeing the password in text when self 
regestering, 
> if I turn this option off when the user changes his password will this 
> password still be seen?

Where did you see the password? Was it on this logbook or on your own? Did 
you use "self register" equal 3 or 2? The password should never be visible 
in plain text, so after you submit it (during registration or login), the 
page gets immediately redirected since the password is contained in the 
URL. After the redirection, it is not visible any more. Now it might happen 
that the redirection takes a few seconds, depending on the network speed, 
then you see it for this few seconds. But in an intranet installation, this 
should not happen.

> 2) I have changed all the files to be owned on my RedHat Server by the 
> user:group as elog:elog and set and moved the logbooks to another 
directory 
> other than in /usr/local/elog namely /home/elog/logbooks, my concern is 
is 
> I was to upgrade to a newer version would it be a simple install over the 
> top? any caveats?

Yes, if you upgrade, the new version will again to into /usr/local/elog 
unless you tell "rpm" to relocate the package. Unfortunately I'm not a 
specialist with "rpm", but you might figure it out yourself (just try to 
reinstall the same version and look where the files go wiht "rpm -ql elog").