Re: A few windows changes

["Eddie Bell" <ejlbell () gmail com>]

I already added the winpcap update to my list because I saw it
involved a security fix! but I will take a look at the versioning
problem as well. If it is relatively simple to do I'll get it
committed today.

thanks
- eddie

On 05/07/07, Fyodor <fyodor () insecure org> wrote:
> On Wed, Jun 06, 2007 at 05:12:44PM +0100, Eddie Bell wrote:
> > 3) Updated winpcap to version 4.0. I have tested this on XP but if any
> > one is using 2k/2k3/vista it would be great if you could try it out.
>
> Hi Eddie.  Your changes look great, but I've encountered a problem
> with the new winpcap-nmap-4.0.exe which is generated.  I already have
> Winpcap 3.1.0.27 installed.  So when I run that new winpcap 4.0
> installer from the mswin32/winpcap directory, I get the proper prompt:
> "WinPcap version 3.1.0.27 exists on this system.  Replace with version
> 4.0.0.755?"  But If I run the same installer exe (or the newly
> generated Nmap installer which includes it) from another directory, I
> get a wrong message: "Skipping WinPcap installation since version
> 3.1.0.27 already exists on this system".
>
> I think the problem is probably that the Installer (generated from
> mswin32/winpcap/winpcap-nmap.nsi ) gets the version it is trying to
> install from wpcap.dll.  If that DLL is in the same directory as the
> install (e.g. when I run the installer from nmap/mswin32/ in SVN),
> everything works fine.  But in the normal case where users are
> installing Nmap, that wpcap.dll won't exist and so an
> already-installed version on the system will be used instead.  So I
> think the solution is for winpcap-nmap.nsi to determine the version it
> is trying to install in a different manner.  Like maybe it can
> determine the version being installed while the installer exe is being
> generated, rather than when it is run on the end users system.
>
> This was probably an existing problem with the installer which we're
> only noticing now because you have upgraded WinPcap and so upgrade
> flaws are more obvious.  But can you try to fix it?  This is important
> for the upcoming Nmap SoC release.  And while you're at it, if you can
> update to the new WinPcap 4.01, that would be great!
>
> Cheers,
> Fyodor

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