mailing list archives
Re: Please help..
From: "Michael Pattrick" <mpattrick () rhinovirus org>
Date: Tue, 10 Jun 2008 18:58:40 -0400
I only sent my last email to Fyodor(oops) so heres a copy:
On Tue, Jun 10, 2008 at 5:10 PM, Fyodor <fyodor () insecure org> wrote:
Hi Michael (and Rob). Do you know which exact DLLs we need?
The DLL is located in C:/windows/WinSxS along with about 40 other DLLs,
there is a trick to find the right one that Microsoft doesn't recommend
anymore. Their current suggested methods are here  and here , but it
may just be easier to package the Nmap installer with the VS C++ runtime
installer(2005 version) (2008 version) like what is already done with
2008 uses more or less the same DLL linking system as 2005.
On Tue, Jun 10, 2008 at 6:38 PM, Rob Nicholls <
robert () everythingeverything co uk> wrote:
From: Fyodor [mailto:fyodor () insecure org]
Hi Michael (and Rob). Do you know which exact DLLs we need? Does
this requirement come from the new Windows SSL support
I just quickly ran depends.exe and it looks like the two OpenSSL DLLs we're
now providing with Nmap require msvcr80.dll to be present. I suspect we
could solve the problem if Kris (or someone) uses static linking when the
OpenSSL DLLs are compiled before they're added to the mswin32\OpenSSL\bin
folder, but we're reaching the limits of my knowledge now.
Static linking may cause problems, Microsoft provides many copies of
'msvcr80.dll' for different CPU's in 'c:\windows\winsxs'. If the compiler is
running on an x86-64 cpu then the application will be statically linked to
the 64bit runtime which may cause problems for 32-bit users. I cant test
this out though and dont have any first hand experience, just my hypothises.
But it could possibly solve a lot of end-user headache and only inflate nmap
by about 1.2megs.
Sent through the nmap-dev mailing list
Archived at http://SecLists.Org