On Wed, Mar 16, 2005 at 04:38:58PM -0500, Paul Melson wrote:
> Just reading your story and thinking back to other Nessus unpleasantries
> I've experienced. When analyzing production networks (especially banks or
> any place with check printers), it's a good idea to do some sort of
> discovery about which IP addresses are used by production printers and
> remove them from the scope of your Nessus tests. Several of the NASL's will
> find open lpd or JetDirect ports and test them for app-layer protocol
> responses (i.e. 'GET / HTTP/1.0^M^M') which will trigger a print job,
> wasting a check and throwing off someone's next check run, ultimately making
> your project unpopular with the locals. Hope that saves somebody somewhere
> a headache.
The plugin dont_scan_printers.nasl should avoid this annoyance.
If you scan printers and Nessus actually performs its job, please send
me the .nsr/.nbe (even .html) report for that printer, so that I can
update the plugin.
-- Renaud
_______________________________________________
Nessus mailing list
[email protected]
http://mail.nessus.org/mailman/listinfo/nessus
