Re: A few windows changes

["Gianluca Varenni" <gianluca.varenni () gmail com>]

----- Original Message ----- 
From: "Fyodor" <fyodor () insecure org>
To: "Eddie Bell" <ejlbell () gmail com>
Cc: "Nmap Dev" <nmap-dev () insecure org>
Sent: Thursday, July 05, 2007 2:29 PM
Subject: Re: A few windows changes


> On Thu, Jul 05, 2007 at 11:54:22AM +0100, Eddie Bell wrote:
> > 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.
>
> Great - I see that you already made the updates in the SoC SVN.  It is
> a little bit of a shame to be hardcoding the Winpcap version number,
> but you make a great point that it already needs to be changed
> manually in other places in the file.  So it isn't much of an added
> burden.
>
> Speaking of WinPcap upgrading, would you write up a file detailing
> everything you need to do for a WinPcap upgrade?  I should have
> suggested this before you did the upgrade so you could take notes
> during the process.  But I think by looking at your CVS checkins you
> should pretty easily be able to ensure that you don't miss any of the
> parts which need changing.  The instructions should then be checked in
> to SNV.  I think
> /nmap-exp/soc07/nmap/mswin32/winpcap/Upgrading-Instructions.txt would
> be a good place.  This will make it a lot easier for you or whoever
> else does the next WinPcap upgrade.
>
> Also, I see that the new system requires a line like:
>
> StrCpy $my_ver "4.0.0.901"
>
> The document should explain the easiest way to get that number.  It
> also seems a little strange that WinPcap 4.0.1 would use the version
> number 4.0.0.901 .

Fyodor,

I can give you an answer for this, because I was the one who decided that 
weird versioning.
There was no plan to release a new stable version of WinPcap containing the 
security issue. I was planning to just release WinPcap 4.1 beta, containing 
that fix and some experimental tweaks to pcap_compile to better support 
wireless filtering (needed for our AirPcap and AirPcap-n adapters). So 
WinPcap 4.1 beta was ready and we actually shipped it to some customers 
before it was live on the web. Then we decided that it was better to have a 
new stable release with just the security fix, and 4.0.1 was the only 
possible way to do that.
As to why the internal version is 4.0.0.901 instead of 4.0.1.901, the reason 
is that the third number in the x.x.x.x version is always set to 0 for the 
vanilla winpcap and to a number != 0 for special builds like winpcap 
professional. This is what I usually call "marketing version vs. engineering 
version" (like windows 2000 vs NT5.0). The important number is always the 
last one, actually, the build number...

Have a nice day
GV









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


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