Nmap Development mailing list archives
Re: Should nmap.set_port_version support name_confidence?
From: Kris Katterjohn <katterjohn () gmail com>
Date: Fri, 24 Oct 2008 23:38:59 -0500
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 10/24/2008 11:13 PM, Brandon Enright wrote:
[Sorry for the top-post, I'm on a phone.] My only counter-argument to setting the fingerprint is that the -sV engine doesn't set it when it finds a match and if the NSE script doesn't get a match the probe->response fingerprint structure and semantics of -sV don't correspond to any moderatly complex script.
Hmm.. this is of course a good point. It's not that I am specifically in favor of adding support for setting the fingerprint, but I feel that if it's not adding any real complexity then having that support is a Good Thing. This is in contrast to something like C/C++ APIs (like older MS ones) that have multiple "reserved" parameters for functions which you must pass NULL into for no reason other than them possibly implementing an option to be passed there in the future. In the case of the fingerprint setting, if it defaults to nil so that not specifically setting it along with the other service information in a script doesn't break anything, it's always there for somebody who finds a use for it. But again you have a valid point here, so I'm certainly not going to fight for this option.
Brandon
Thanks, Kris Katterjohn -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iQIVAwUBSQKi4P9K37xXYl36AQK1Ow/+LR+VRPs2iXN8ExL/VyKK5FnswXVOLDJR ALtpz4mWSJR1x94qf0AhpMdqNQvlYY4J3VZVUWSKGtyM8IqIkk580kIo2E29imy3 GAhVLN19bevLIRqll3K6at4yLL0XHLYYFk/qWT1ePrfvF8ikVUBxhATf1/WEY5lF X7efT/nXjONm6blg8IOLQhe5Ska4/s9Xc7S80jGjxLk9Fj2PaO8wvoJIb7vYb4Lm sxP2Fq/DsCzKRBtyt6AxkdtA7sshJ8ycQY8VX1tJr0zNvfX7pH2CeTt7vq7/xpxK +7c9C+DIgh+w/eYUKcWfeGuOvwkOxt+KhR6/Ep7R7nstm0HEq9HODIvpBM9X55Vr pCNsbB7/Tz/+U4FsyQpnK75XnwmO1HpxcQtNlpgYlRPhFNTCQfbjfqjdaEh8I7kk 8tunqo0yBXK8brqzaWw16lhYySnT5JO7cEa3Zs3d+0tgs7EXY8tvZnfddmx1GIhB 4udwX9OnELM+0N23cDrrz6PRtVmjzi5PKzEY7JZqHaeRDA0kXs9McnJfxpgnEMZu +liE7d3sNvCVz50s/+jjkBF9a0etPOsUuz9FQKU25Qu48cGO+GrZfkA7dDrWwgKB p3RY86izf30zT2/BhmGClb4xiwtNO5EGJ2OZF/blYUf/U2hmDeuxVeWRsAUXSFX/ J4c5SNTJJhE= =I5UW -----END PGP SIGNATURE----- _______________________________________________ Sent through the nmap-dev mailing list http://cgi.insecure.org/mailman/listinfo/nmap-dev Archived at http://SecLists.Org
Current thread:
- Should nmap.set_port_version support name_confidence? David Fifield (Oct 24)
- Re: Should nmap.set_port_version support name_confidence? Brandon Enright (Oct 24)
- Re: Should nmap.set_port_version support name_confidence? Kris Katterjohn (Oct 24)
- Re: Should nmap.set_port_version support name_confidence? Brandon Enright (Oct 24)
- Re: Should nmap.set_port_version support name_confidence? Kris Katterjohn (Oct 24)
- Re: Should nmap.set_port_version support name_confidence? David Fifield (Oct 25)
- Re: Should nmap.set_port_version support name_confidence? Kris Katterjohn (Oct 24)
- Re: Should nmap.set_port_version support name_confidence? David Fifield (Nov 20)
- Re: Should nmap.set_port_version support name_confidence? Brandon Enright (Oct 24)