Demo Discussion
Forum Config Examples Contributions Vulnerabilities
  Discussion forum about ELOG, Page 757 of 808  Not logged in ELOG logo
    icon2.gif   Re: Problems with 2.3.2, posted by Stefan Ritt on Thu Mar 13 17:33:58 2003 
> 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 
    icon2.gif   Re: Problems with 2.3.2, posted by Stefan Ritt on Fri Mar 14 10:30:25 2003 
> > 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 
icon1.gif   Elog and SSL, posted by Recai Oktas on Sun Mar 16 19:15:16 2003 stunnel_with_smtp_pop3.txt
> Basically im running elog on a redhat 8 box with stunnel already installed 
> as part of OpenSSL, on the server i ran the command specified in the 
> instructions
    icon2.gif   Re: Elog 2.3.3, problems of 2.3.2 solved, posted by djek on Thu Mar 20 21:07:09 2003 
> > After upgrading from 2.3.1 to 2.3.3, elog is not able to load any resources
> > as stylesheets, images or passwordfiles.
> > 
    icon2.gif   Re: Elog 2.3.3, problems of 2.3.2 only partly solved, posted by Stefan Ritt on Thu Mar 20 21:07:09 2003 
> After upgrading from 2.3.1 to 2.3.3, elog is not able to load any resources
> as stylesheets, images or passwordfiles.
icon12.gif   Elog 2.3.3, problems of 2.3.2 only partly solved, posted by djek on Thu Mar 20 21:07:09 2003 
After upgrading from 2.3.1 to 2.3.3, elog is not able to load any resources
as stylesheets, images or passwordfiles.
    icon2.gif   Re: Elog and SSL, posted by Stefan Ritt on Fri Mar 21 16:24:05 2003 
> I was wondering if you can help me understand the concept and if i am doing 
> something wrong with securing Elog via SSL
    icon2.gif   Re: Re: Elog and SSL, posted by Recai Oktas on Fri Mar 21 16:52:12 2003 
Ooops, I destroyed the original post, now how can we fix this :)
ELOG V3.1.5-3fb85fa6