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

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


Author: mwiegand
Date: 2008-09-18 15:59:16 +0200 (Thu, 18 Sep 2008)
New Revision: 1374

Modified:
   trunk/openvas-compendium/ChangeLog
   trunk/openvas-compendium/openvas-compendium.tex
Log:
* openvas-compendium.tex: Added information about sladinstaller, updated
protocol specification.


Modified: trunk/openvas-compendium/ChangeLog
===================================================================
--- trunk/openvas-compendium/ChangeLog	2008-09-18 12:28:44 UTC (rev 1373)
+++ trunk/openvas-compendium/ChangeLog	2008-09-18 13:59:16 UTC (rev 1374)
@@ -1,5 +1,10 @@
 2008-09-18  Michael Wiegand <michael.wiegand at intevation.de>
 
+	* openvas-compendium.tex: Added information about sladinstaller, updated
+	protocol specification.
+
+2008-09-18  Michael Wiegand <michael.wiegand at intevation.de>
+
 	* openvas-compendium.tex: Put URLs in hyperurl environments, added
 	clarification regarding configuration, added OVAL/ovaldi information,
 	fixed typos.

Modified: trunk/openvas-compendium/openvas-compendium.tex
===================================================================
--- trunk/openvas-compendium/openvas-compendium.tex	2008-09-18 12:28:44 UTC (rev 1373)
+++ trunk/openvas-compendium/openvas-compendium.tex	2008-09-18 13:59:16 UTC (rev 1374)
@@ -2027,6 +2027,15 @@
 a PDF out of this html report. Depending on the version and features
 the created links in the PDF file may be created differently.
 
+\xname{client-sladinstaller}
+\subsection{Installing SLAD using SLADinstaller}
+
+If you are planning to use the Security Local Auditing Daemon (SLAD) with
+OpenVAS (as described in section \ref{sec:slad}), there is a convenient way to
+install SLAD on a local or remote machine. Using the ``SLAD install'' option in
+the file menu, you can launch the \verb|sladinstaller| binary from within
+OpenVAS-Client, which will the guide you through the installation process.
+
 \clearpage
 
 \xname{performing-local-security-checks}
@@ -2039,7 +2048,8 @@
 this procedure has been tested only with Debian local security checks.
 
 \xname{prerequisites-dlsc}
-\subsection{Prerequisites} 
+\subsection{Prerequisites}
+\label{sec:deb-lsc-prereqs}
 
 To perform local security checks, you need a working OpenVAS-Server
 installation. Information on setting up and configuring OpenVAS-Server is
@@ -2195,12 +2205,14 @@
 
 \xname{using-integrated-tools}
 \chapter{Using Integrated Tools}
+\label{chap:tools}
 
 \xname{security-local-auditing-daemon}
 \section{Security Local Auditing Daemon (SLAD)}
 \compendiumauthor{Jan-Oliver Wagner}
 \xname{how-to-use-slad-with-openvas}
 \subsection{How to use Security Local Auditing Daemon (SLAD) with OpenVAS}
+\label{sec:slad}
 
 Homepage: \hyperurl{http://www.dn-systems.org/slad.shtml}
 
@@ -2237,7 +2249,8 @@
 helpful hints.
 
 \item Prepare SSH Authorization: It is required to use a SSH key created
-following the example for ssh-keygen and openssl on the page about local
+following the example for ssh-keygen and openssl in section
+\ref{sec:deb-lsc-prereqs} on page \pageref{sec:deb-lsc-prereqs} about local
 security checks. Especially take care you create a RSA .p8 key file. Reason:
 sladinstaller would else create a key that is not usable with OpenVAS due to the
 migration from OpenSSL to GNU/TLS.
@@ -4042,16 +4055,14 @@
 \xname{otp-initialization-and-features}
 \section{Protocol Initialization and Protocol Features}
 
-The client start the protocol with a initializer of the protocol version
-followed by parameters switching on various features. Available protocol
-features are:
-\begin{itemize}
- \item md5\_caching (server will use the MD5 caching feature)
-\end{itemize}
+The client will start a protocol session by sending a version string specifying
+the requested protocol version to the server. Upon receiving this string, the
+server may answer with the same version string if it supports the requested
+protocol version or terminate the connection.
 
 Syntax:
 \begin{verbatim}
-< OTP/1.0 >< protocol_feature1 protocol_feature2 ... >
+< OTP/1.0 >
 User : user_name
 Password : user_password
 \end{verbatim}
@@ -4089,8 +4100,8 @@
 \subsection{COMPLETE\_LIST}
 
 \paragraph{Description:}
-This command can be used by the client in case the protocol feature
-"md5\_caching" was selected by the client.
+This command can be used by the client to request the complete list of plugins
+from the server.
 
 It usually follows the \verb|PLUGINS_MD5| commands of the server in case the
 server side md5sum is not equal to the md5sum of the client side cached NVTs.
@@ -4137,12 +4148,11 @@
 \subsection{GO ON}
 
 \paragraph{Description:}
-This command can be used by the client in case the protocol feature
-"md5\_caching" was selected by the client. It usually follows the
-\verb|PLUGINS_MD5| commands of the server in case the server side md5sum is
-equal to the md5sum of the client side cached NVTs. The server will answer with
-command \verb|PREFERENCES| and communication will continue as it would have been
-without md5\_caching feature.
+This command can be used by the client to confirm that the plugin information
+has been received and to signal to the server that it may proceed. It usually
+follows the \verb|PLUGINS_MD5| commands of the server in case the server side
+md5sum is equal to the md5sum of the client side cached NVTs. The server will
+answer with command \verb|PREFERENCES| and communication will continue.
 
 \paragraph{Syntax:}
 



More information about the Openvas-commits mailing list