I've had encountered numerous troubles when VS 2005 came out,
with it's so called 'side-by-side assemblies'...
having often to mess around with custom-made manifest files etc.,
and even then,not always successfully,
as there were way too many incorrectly compiled programs distributed out there...
But now I was just reading the page over at Shining Light,and it says:
Although there is a "newer version" of this installer, this is the correct version to install.
That's kinda weird...because assuming the .exes are compiled correctly in the first place,
newer Visual C++ redistributables shouldn't 'break' them...at the worst case scenario,
a .manifest file should be created to point/redirect to the newer libraries:
http://msdn.microsoft.com/en-us/library/aa375632.aspx...should I assume that older OpenSSL dlls were not compiled with VS2005/2008?
Question is: could OpenSSL be compiled statically into Malzilla.exe itself,
in order to see if the problem persists?Not sure if this is possible...plus,one more idea:
http://www.stunnel.org/download/stunnel/win32/stunnel-4.26-installer.exelibeay.dll included there is OpenSSL 0.9.8i -> build 15 Sep 2008 with gcc...
