Re: Please help..

["Michael Pattrick" <mpattrick () rhinovirus org>]

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[1] that Microsoft doesn't recommend
anymore. Their current suggested methods are here [2] and here [3], but it
may just be easier to package the Nmap installer with the VS C++ runtime
installer[4](2005 version) [5](2008 version) like what is already done with
Winpcap.

2008 uses more or less the same DLL linking system as 2005.


Chars,
Michael

[1] http://blogs.msdn.com/nikolad/archive/2005/03/18/398720.aspx
[2] 
http://msdn.microsoft.com/en-us/library/ms235317(VS.80).aspx<http://msdn.microsoft.com/en-us/library/ms235317%28VS.80%29.aspx>
[3] 
http://msdn.microsoft.com/en-us/library/ms235291(VS.80).aspx<http://msdn.microsoft.com/en-us/library/ms235291%28VS.80%29.aspx>
[4]
http://www.microsoft.com/downloads/details.aspx?familyid=32bc1bee-a3f9-4c13-9c99-220b62a191ee&displaylang=en
[5]
http://www.microsoft.com/downloads/details.aspx?familyid=9B2DA534-3E03-4391-8A4D-074B9F2BC1BF&displaylang=en


On Tue, Jun 10, 2008 at 6:38 PM, Rob Nicholls <
robert () everythingeverything co uk> wrote:

> > -----Original Message-----
> > From: Fyodor [mailto:fyodor () insecure org]
> <snip>
> > 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.


Cheers,
Michael

_______________________________________________
Sent through the nmap-dev mailing list
http://cgi.insecure.org/mailman/listinfo/nmap-dev
Archived at http://SecLists.Org