Quoting Javier Fernández-Sanguino Peña <jfernandez@germinus.com>:
> I'm aware of the problems using banners, there are also issues regarding
> port-redirection, NAT, etc. that might taint the view. However, you
> misinterpreted me. This would not be a test to run others, it would be a
> "do_it_when_all_tests_are_done" and would just try to determine what's
> behind a given IP address. No need for an "ignore host" since I'm not
> talking about a test that uses this information (at the moment :) and if
> there was then this test should not run in the ACT_END phase.
I'm a bit slow, but I'm with you now ;)
That's a decent idea... attempting to ident the remote machine based on the
other test results (it would have to be weighted, I am assuming). We could also
considering adding an xprobe/xprobe2 plugin (it seems to do a good job) along
with the nmap ident.
> I'm aware of the problems using banners, there are also issues regarding
> port-redirection, NAT, etc. that might taint the view. However, you
> misinterpreted me. This would not be a test to run others, it would be a
> "do_it_when_all_tests_are_done" and would just try to determine what's
> behind a given IP address. No need for an "ignore host" since I'm not
> talking about a test that uses this information (at the moment :) and if
> there was then this test should not run in the ACT_END phase.
I'm a bit slow, but I'm with you now ;)
That's a decent idea... attempting to ident the remote machine based on the
other test results (it would have to be weighted, I am assuming). We could also
considering adding an xprobe/xprobe2 plugin (it seems to do a good job) along
with the nmap ident.