[Openvas-commits] r2587 - trunk/doc

[scm-commit@wald.intevation.org]

Author: lmwangi
Date: 2009-02-26 11:58:17 +0100 (Thu, 26 Feb 2009)
New Revision: 2587

Modified:
   trunk/doc/INSTALL
   trunk/doc/TODO
   trunk/doc/overview.txt
Log:
Adding dependency requirements to INSTALL

Modified: trunk/doc/INSTALL
===================================================================
--- trunk/doc/INSTALL	2009-02-26 10:00:19 UTC (rev 2586)
+++ trunk/doc/INSTALL	2009-02-26 10:58:17 UTC (rev 2587)
@@ -1,8 +1,9 @@
 Basic Installation
 ==================
 Dependencies
- * GNUTLS
- * libpcap ??
+ * gnutls-dev
+ * libpcap-dev
+ * libgpgme-dev
 
 
 1. Build openvas-libraries 

Modified: trunk/doc/TODO
===================================================================
--- trunk/doc/TODO	2009-02-26 10:00:19 UTC (rev 2586)
+++ trunk/doc/TODO	2009-02-26 10:58:17 UTC (rev 2587)
@@ -1,4 +1,20 @@
 openvas-server
 openvasd/openvasd.c:1233: Copyright. Needs to be fixed. IANAL.. but i think it should also mention SPI
+memleak in openvas-client
+valgrind says:
+==7906== ERROR SUMMARY: 4327 errors from 5 contexts (suppressed: 39 from 2)
+==7906== malloc/free: in use at exit: 21,444,239 bytes in 255,797 blocks.
+==7906== malloc/free: 890,031 allocs, 634,234 frees, 163,300,733 bytes allocated.
+==7906== For counts of detected errors, rerun with: -v
+==7906== searching for pointers to 255,797 not-freed blocks.
+==7906== checked 20,621,056 bytes.
+==7906== 
+==7906== LEAK SUMMARY:
+==7906==    definitely lost: 374,328 bytes in 10,259 blocks.
+==7906==      possibly lost: 611,721 bytes in 712 blocks.
+==7906==    still reachable: 20,458,190 bytes in 244,826 blocks.
+==7906==         suppressed: 0 bytes in 0 blocks.
+==7906== Rerun with --leak-check=full to see details of leaked memory.
 
 
+

Modified: trunk/doc/overview.txt
===================================================================
--- trunk/doc/overview.txt	2009-02-26 10:00:19 UTC (rev 2586)
+++ trunk/doc/overview.txt	2009-02-26 10:58:17 UTC (rev 2587)
@@ -29,7 +29,7 @@
 
 OpenVAS plugins
 ------------------------
-Plugins are typically written in NASL. Typically, there's a 1-1 relationship between a plugin and a vulnerability. The detachment of plugins[Vulnerability list] from the scanner itself enables plugin development to be decoupled from the scanning engine development. Thus we can have plugins released and updated daily in a similar fashion to debian apt tool.
+Plugins are typically written in NASL. Typically, there's a 1-1 relationship between a plugin and a vulnerability. The detachment of plugins[Vulnerability list] from the scanner itself enables plugin development to be decoupled from the scanning engine development. Thus we can have plugins released and updated daily in a similar fashion to the debian apt tool.
 
 A typical plugin has
  * A description of what the plugin does
@@ -96,6 +96,12 @@
 Now write a simple nasl script to check for telnet availability.
 Compare your results with 'openvas-plugins/scripts/telnetserver_detect_type_nd_version.nasl'
 
+You may use the openvas-nasl tool to verify it's syntax as well as execute it.
+A typical example is
+$ sudo openvas-nasl telnetserver_detect_type_nd_version.nasl -t localhost -X
+
+A pcap tool such as wireshark can be used while debugging your script
+
 At startup, openvasd loads (?and compiles?) all the nasl scripts specified in it's config file. The scripts are categorized into various groups (?Prescan, Postscan, Safechecks etc...?). Depending on the category, and user settings, openvasd will load a [sub]set of the plugin scripts for checks. For example:
 Prescan : Check whether host is up
 Scan:  Check whether plugin is safe vs user setting; Run the script if all's ok