Re: NSE output verbosity (p2p-conficker)

[Kris Katterjohn <katterjohn () gmail com>]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Fyodor wrote:
> Another idea is to make it easy for scripts to tell if they were
> specified by name on the command line.  Then they could increase their
> personal verbosity level a couple points.  That way the detailed
> p2p-conficker results could only be printed if -vv or if the user
> specified something like "--script p2p-conficker" on the command line,
> but not for a default script scan.  The theory behind this is that
> someone who specifies p2p-conficker on the command line is showing a
> particular interest in that script and likely wants to see proof that
> it has run, etc.  But someone who just gets p2p-conficker by default
> is less likely to want an "all clean" report from every default
> script.

I like this idea!  I agree that calling a script specifically can be a real
sign of a desire for increased output.

> Cheers,
> -F

Thanks,
Kris Katterjohn

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iQIcBAEBAgAGBQJKJxSDAAoJEEQxgFs5kUfumakQAKlrk5VtlcPTxgqP/hf8eC3m
9/kAM9QJkl+q8qjkd0GZtXOmw5hG7hzmTWmUeelDex3jrF8VAPnIBXPsjyrisWUy
Iqls4pH3NjPqN7QgvlBoEfjPHdGNsXnSEX8kOhuc3UtAXv5ZUxcyjn3HFgRKmzVo
o3LT2QFe/F5fZZ2rrfi56yKbyQuaOh/eZulMT3RDPD8CVtMuIJrQh08iOrDUmTy1
FrElhC0ynpcdE5WUA81Fv5ZXGXdN4ErdF28Dd+Pp7EDlNIg/OgbVBIrjF9nG2v9K
Kj0mFvdK0rW/JvWO6lnDkpPUN8gpbLC2ZHT8fh2zu3rhxXEWdJSM3NF8uWLgBWkq
eyFIRSFpBCxFJG2vc0QyxaXn7lSbEUn0oRCkD4yEFjxe/KemKzKrXngRPHLTJRub
SEB8f1SmQhxW6B24GHJdO74yvNAGaOPEsvxktBK5d1DBUt0Kh0C3S/LUXDrfrx4K
u/HL3NhbzAPxyjj6ERO5qJO0bJbEbOU0S7Uu0IpJn5xyUefKdhsMTsOlIh4wKq1P
ocTNjztvE7efDKSGpfaXuBi4s4FVKev9Y9DSN8z/MK7Zz5jyb+4RroFqKVxSLZCA
VAc71vk9ENXexZOTMX4ltUaL57NeS1/0FDOIp5gaMQ3LxLn3KYFlphU+2Z5SWfk1
U9VEtFGu2+ycpvDvdBsg
=OVx9
-----END PGP SIGNATURE-----

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