Demo Discussion
Forum Config Examples Contributions Vulnerabilities
  Discussion forum about ELOG  Not logged in ELOG logo
icon4.gif   Elog does not work after installing MS12-006/MS12-012 on Win 7, posted by Allen on Wed Jan 11 22:19:49 2012 
    icon2.gif   Re: Elog does not work after installing MS12-006/MS12-012 on Win 7, posted by Allen on Thu Jan 12 19:34:28 2012 
       icon2.gif   Re: Elog does not work after installing MS12-006/MS12-012 on Win 7, posted by Allen on Thu Jan 12 19:37:52 2012 
          icon2.gif   Re: Elog does not work after installing MS12-006/MS12-012 on Win 7, posted by Stefan Ritt on Fri Jan 13 14:33:04 2012 
Message ID: 67162     Entry time: Thu Jan 12 19:37:52 2012     In reply to: 67161     Reply to this: 67163
Icon: Reply  Author: Allen  Author Email: bastss@rit.edu 
Category: Bug report  OS: Windows  ELOG Version: 2.9.0-2396 
Subject: Re: Elog does not work after installing MS12-006/MS12-012 on Win 7 

Allen wrote:

Allen wrote:

After patching a windows 7 computer with MS12-006, can no longer connect to elog, get page cannot be displayed

See

http://support.microsoft.com/kb/2643584

 A little more information here

We are running elog on an Ubuntu server

Elog was working fine, then, on a windows 7 machine, MS12-006 was installed, rebooted, and could no longer connect to the elog web page.

Discovered that in Internet Explorer 8, by unchecking the use TLS 1.0 in options advanced tab, and making sure that SSL 3.0, TLS 1.1, TLS 1.2 were checked, that the page once again worked.  I'm guessing the elog does not support SSL 3.0, otherwise, I assume I would have to uncheck that as well.  Things do appear to still work on XP, thus far, only Windows 7 appears to break.  While we have a work around, ideally we would like to see a bug fix so that (for legacy reasons), elog will still work with TLS 1.0 on Windows 7.

 

 Also, strangely, I am able to use the elog forum page https://midas.psi.ch/elogs/Forum while TLS 1.0 is checked.  I notice the version number is 2.9.0-2425, while we are using 2.9.0-2396, so wondering if this is fixed in this newer version.

ELOG V3.1.5-fe60aaf