Re: [PATCH] Update to nmap-rpc

[Daniel Miller <bonsaiviking () gmail com>]

On 03/10/2011 03:48 PM, David Fifield wrote:
> On Wed, Mar 09, 2011 at 01:49:31PM -0600, Daniel Miller wrote:
> > Hi list,
> >
> > I've attached a diff for the nmap-rpc file based on the latest
> > assignments. RFC 5531 switched authority for assignments from Sun to
> > IANA, and they have an XML feed of the latest (2010-06-16)
> > assignments. Many of these were the same, a few had new information,
> > and some were new. By my count, I modified 42 lines (adding
> > information only, not removing) and added 1270 (not including some
> > documentation at the top).
> >
> > To make it easier for others to check my work, I'll also attach the
> > python script I used to parse the IANA XML.
> Thanks Daniel! This is great.
>
> I'm trying to reproduce your output to make this easy to update in the
> future. How much manual editing did you have to do of the output? The
> first line of output is
>
> pmapprog        100000  portmap rpcbind #portmapper
>
> while in the diff you sent, it's
>
> rpcbind         100000  portmap sunrpc rpcbind #portmapper
>
> Currently the line is
>
> rpcbind         100000  portmap sunrpc rpcbind
>
> David Fifield
I did a fair amount of manual editing, always assuming that the Nmap 
information was accurate as seen "in the field." I used the attached 
Perl script to produce a semi-merged version. It preserves ordering by 
program number. Conflicting lines are printed side-by-side, with the one 
coming from "newrpc" (the generated file) prefixed with ">". Then I just 
searched through the file for /^>/ and made manual decisions from then 
on. My basic criteria for merging were:

   * Keep Nmap's name for the service (since most were ones I
     recognized as accepted)
   * Any new names or aliases that differed in more than just "*d" or
     "*prog", add as new aliases
   * If the comment was more than just the name spelled out (i.e.
     ypservd #yp server daemon), add the comment to the end
   * If there is an existing comment, preserve it.

I wish there was an easy way to update this, but since the IANA list 
hadn't changed since June 2010, it shouldn't be too often that it needs 
to be done. Also, I was disappointed with the quality of the IANA list 
(misspelled words, strange naming convention, etc.)

Dan

Attachment: merge.pl
Description:

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