http-php-version output

["Rob Nicholls" <robert () robnicholls co uk>]

I'm slowly working my way through every version of PHP 5 on Windows (just
the 5.3.x variants left now!) to generate some new hashes for the script.
This has led to quite a few "duplicate" values because we're also listing OS
specific variants such as "5.2.4-2ubuntu5.10" and "5.2.12-0dotdeb.1" when
there's already an existing value of "5.2.4" and "5.2.9 - 5.2.14" against
exactly the same respective hashes.

Would it be okay to ditch the OS variant? Would people be happy knowing that
it matches a particular version of PHP rather than
5.2.4.%everyLinuxVariantSomeoneSpots%?

For example, I'd change:

["6a1c211f27330f1ab602c7c574f3a279"] = {"5.2.0", "5.2.0-8-etch13 -
5.2.0-8-etch16"},
to
["6a1c211f27330f1ab602c7c574f3a279"] = {"5.2.0"},

I don't think we've lost anything by removing it. We certainly don't gain
anything, except perhaps confusion (especially when testing a Windows host),
by having the Debian variant listed.

Also, would people find it more useful having:

{"5.2.9 - 5.2.14"}
Or
{"5.2.9", "5.2.10", "5.2.11", "5.2.12", "5.2.13", "5.2.14"}

I think that's the worst case example if they're expanded.

I don't particularly like the idea of 5.2.x as it feels vague (I know that
more specific, typically lower, versions are detected due to their different
hashes). Grouping them together works, but the script inconsistently uses
dashes and "to" - I propose replacing them all with dashes if we go this
route, which is more consistent with Nmap's OS detection, e.g. "Linux 2.6.13
- 2.6.31".

Having all of the version numbers listed separately could be useful for
people that want to look up known vulnerabilities in specific versions,
without having to parse "4.4.2 - 4.4.4" to spot "4.4.3" in the middle.

I'm leaning towards grouping them though. Thoughts?

Rob


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