[PATCH] Visual C++ 2008 Runtime Components

["Rob Nicholls" <robert () everythingeverything co uk>]

The first patch updates Nmap's Windows setup file to silently install the
correct version of the Visual C++ 2008 runtime components, which are
required by Nmap. I assumed it could find vcredist_x86.exe and
vcredist_x64.exe in the mswin32 folder, but they might deserve their own
folder to keep things tidy. The files are available from:

http://www.microsoft.com/downloads/details.aspx?familyid=9B2DA534-3E03-4391-
8A4D-074B9F2BC1BF
and
http://www.microsoft.com/downloads/details.aspx?familyid=BD2A6171-E2D6-4230-
B809-9A8D7548C1B6

I briefly tested the installer on Vista x86 and Server 2008 x64, and it
seems to work okay (although there appears to be a known problem with
vcredist leaving temp files in the root of the drive[1]).

I should point out that Microsoft's installer requires Windows Installer 3.0
or later, but I'd be a bit surprised if anyone didn't already have it
installed. It's built into Windows XP SP2, WI3.1 is built into Server 2003
SP1, WI4.0 is built into Vista, and you can install WI3.0 on Windows 2000
SP3/SP4 and XP RTM/SP1 and 2003 RTM. IIRC Windows Update requires WI3.0 (or
possibly 3.1 now?). If it becomes an issue, we could probably include the
WI3.1v2 redistributable package, but I think that might be going too far.

Should we include the two vcredist files in Nmap's zip file, like we now do
with the WinPcap setup file? If we're including it as a core file in the
setup file, I suspect it should be part of the zip too, which is why I've
attached a second patch that adds a (wildcarded) line to the Makefile that
should pick up the two vcredist files so they get included in the zip -
again, assuming they're present in the mswin32 folder.


Rob

[1]
http://connect.microsoft.com/VisualStudio/feedback/ViewFeedback.aspx?Feedbac
kID=316557

Attachment: nmap-installer-vcredist2008.diff
Description:

Attachment: nmap-mswin32-makefile-vcredist.diff
Description:

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