[Openvas-commits] r1376 - trunk/openvas-compendium

scm-commit@wald.intevation.org scm-commit at wald.intevation.org
Thu Sep 18 16:17:05 CEST 2008


Author: mwiegand
Date: 2008-09-18 16:17:04 +0200 (Thu, 18 Sep 2008)
New Revision: 1376

Modified:
   trunk/openvas-compendium/ChangeLog
   trunk/openvas-compendium/openvas-compendium.tex
Log:
* openvas-compendium.tex: Added note explaining protocol status.


Modified: trunk/openvas-compendium/ChangeLog
===================================================================
--- trunk/openvas-compendium/ChangeLog	2008-09-18 14:04:59 UTC (rev 1375)
+++ trunk/openvas-compendium/ChangeLog	2008-09-18 14:17:04 UTC (rev 1376)
@@ -1,5 +1,9 @@
 2008-09-18  Michael Wiegand <michael.wiegand at intevation.de>
 
+	* openvas-compendium.tex: Added note explaining protocol status.
+
+2008-09-18  Michael Wiegand <michael.wiegand at intevation.de>
+
 	* openvas-compendium.tex: Updated protocol specification.
 
 2008-09-18  Michael Wiegand <michael.wiegand at intevation.de>

Modified: trunk/openvas-compendium/openvas-compendium.tex
===================================================================
--- trunk/openvas-compendium/openvas-compendium.tex	2008-09-18 14:04:59 UTC (rev 1375)
+++ trunk/openvas-compendium/openvas-compendium.tex	2008-09-18 14:17:04 UTC (rev 1376)
@@ -2345,10 +2345,8 @@
 newer versions you may need to manually evaluate whether the threats reported
 by Nikto are real threats or simply the result of the web server configuration.
 
-\clearpage
-
 \xname{ovaldi}
-\section{Ovaldi}
+\section{Ovaldi (OVAL support in OpenVAS)}
 \label{sec:ovaldi}
 
 \compendiumauthor{Michael Wiegand}
@@ -4032,6 +4030,12 @@
 
 \xname{openvas-transfer-protocol}
 \chapter{OpenVAS Transfer Protocol (OTP)}
+
+\textbf{Note: The OpenVAS Transfer Protocol was introduced in version 2.0 beta.
+Be aware that the information presented represents the current state of OTP,
+which is still under heavy development. This notice will be removed once the
+OTP specification has been finalized.}
+
 The client and the server module in an OpenVAS installation communicate through
 the OpenVAS Transfer Protocol (OTP). Earlier versions of OpenVAS have used the
 Nessus Transport Protocol (NTP) inherited from Nessus, but in order to address



More information about the Openvas-commits mailing list