Nmap Development mailing list archives

Re: Nmap/Ncat 5.50 Dependency Change


From: Rob Nicholls <robert () robnicholls co uk>
Date: Tue, 15 Mar 2011 17:30:10 +0000

Hi David,

Thanks for the link, it could be useful for people that want to run Nmap on unsupported (by Microsoft) versions of Windows. A different suggestion was made at the end of last year, which sounds a little less "hackish", but I don't think anyone here has tried it:

http://seclists.org/nmap-dev/2010/q4/436

The decision to drop support for Windows 2000 wasn't taken lightly, I know Fyodor is always keen to support as many older systems as we can; but we need to balance support for unsupported operating systems against all of the other potential benefits, such as increased security, while trying to keep the build process relatively straightfoward.

You're correct that we should revisit the documentation, as the "Windows 2000 Dependencies" section obviously no longer applies. It should be possible to replace it with a new section on how to compile Nmap for unsupported operating systems, assuming someone can verify a method that works successfully (as there's no point in writing instructions that don't work!).

Cheers,

Rob

On Tue, 15 Mar 2011 05:22:50 -0700 (PDT), David Millis wrote:
From the Nmap/Ncat 5.50 announcement:
"Updated the Windows build process to work with (and require) Visual
C++ 2010 rather than 2008."

By default, Visual Studio 2010 does not create applications that can
run on Windows 2000, Windows XP up to SP1, and Windows Server 2003
RTM. This is because a few extraneous functions were introduced in
later versions of kernel32.dll. The page below provides the means to
prevent incidental linkage against those functions and avoid dll hell.


http://tedwvc.wordpress.com/2010/11/07/how-to-get-visual-c-2010-mfc-applications-to-run-on-windows-2000/

If you decide not to bother and instead drop support for those
systems, the trick this person discovered is interesting, potentially
applicable to other situations.

In any case, the docs should reflect the current situation.
http://nmap.org/book/inst-windows.html#inst-win-source


David




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


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


Current thread: