Nmap Development mailing list archives
Re: [PATCH]in big-endian platform, nmap failed to resolve the service name
From: John Spencer <maillist-nmap () barfooze de>
Date: Tue, 25 Sep 2012 15:18:44 +0200
On 09/25/2012 07:11 AM, David Fifield wrote:
Thank you for finding this. I looked into the problem and decided that there was more wrong than just the hard-coded insertion into bucket 0. The bigger problem was the call protno = htons(protno); which mapped byte values into integers like 0x0100, 0x0200, 0x0300, .... This caused all protocols to end up in bucket 0, even with your fix. I committed a more extensive revision in r29859.
i'd like to integrate this patch into my distribution.what are the options to get this patch without having to checkout the entire svn tree ? is there some svnweb or gitweb (i.e. from a git mirror automatically created with git-svn) interface that can be used to inspect the commit and download the raw patch ?
_______________________________________________ Sent through the nmap-dev mailing list http://cgi.insecure.org/mailman/listinfo/nmap-dev Archived at http://seclists.org/nmap-dev/
Current thread:
- [PATCH]in big-endian platform, nmap failed to resolve the service name hejianet (Sep 24)
- Re: [PATCH]in big-endian platform, nmap failed to resolve the service name David Fifield (Sep 24)
- Re: [PATCH]in big-endian platform, nmap failed to resolve the service name John Spencer (Sep 25)
- Re: [PATCH]in big-endian platform, nmap failed to resolve the service name Matt Selsky (Sep 25)
- Re: [PATCH]in big-endian platform, nmap failed to resolve the service name David Fifield (Sep 25)
- Re: [PATCH]in big-endian platform, nmap failed to resolve the service name John Spencer (Sep 25)
- Re: [PATCH]in big-endian platform, nmap failed to resolve the service name David Fifield (Sep 24)