I tested it with RealVNC 3.3.7 & 4.1, and TightVNC. Seems to work. I added a function to network_func.inc by the way, so do not forget the patch. 1. Should this be merged with vnc.nasl (or should vnc.nasl be deprecated?) 2. Should the report be more precise when an insecure VNC is connected to a LAN, or worse, to a public network? Currently, it only uses security note / warning / hole.
_______________________________________________ Plugins-writers mailing list Plugins-writers@private http://mail.nessus.org/mailman/listinfo/plugins-writers
This archive was generated by hypermail 2.1.3 : Fri Jul 22 2005 - 04:14:39 PDT