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

scm-commit@wald.intevation.org scm-commit at wald.intevation.org
Thu Sep 18 14:28:44 CEST 2008

Author: mwiegand
Date: 2008-09-18 14:28:44 +0200 (Thu, 18 Sep 2008)
New Revision: 1373

* openvas-compendium.tex: Put URLs in hyperurl environments, added
clarification regarding configuration, added OVAL/ovaldi information,
fixed typos.

Modified: trunk/openvas-compendium/ChangeLog
--- trunk/openvas-compendium/ChangeLog	2008-09-18 10:37:49 UTC (rev 1372)
+++ trunk/openvas-compendium/ChangeLog	2008-09-18 12:28:44 UTC (rev 1373)
@@ -1,5 +1,11 @@
 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.
+2008-09-18  Michael Wiegand <michael.wiegand at intevation.de>
 	* openvas-compendium.tex: Added chapter regarding file locations.
 2008-09-17  Michael Wiegand <michael.wiegand at intevation.de>

Modified: trunk/openvas-compendium/openvas-compendium.tex
--- trunk/openvas-compendium/openvas-compendium.tex	2008-09-18 10:37:49 UTC (rev 1372)
+++ trunk/openvas-compendium/openvas-compendium.tex	2008-09-18 12:28:44 UTC (rev 1373)
@@ -139,7 +139,8 @@
 The source format of this document is \LaTeX with Hyper\LaTeX extensions for
 HTML output. The sources are available as module ,,openvas-compendium''
-at the OpenVAS development platform\footnote{http://wald.intevation.org/projects/openvas}.
+at the OpenVAS development
 \section{About the OpenVAS Project}
@@ -240,7 +241,7 @@
 The OpenVAS project maintains a feed of its own:
-  http://www.openvas.org/openvas-nvt-feed.html
+  \hyperurl{http://www.openvas.org/openvas-nvt-feed.html}
 To evaluate your need for an up-to-date feed service, you should think about
 the following questions:
@@ -555,6 +556,15 @@
 \label{sec:Configuring OpenVAS-Server} 
 \compendiumauthor{Michael Wiegand}
+After installing OpenVAS-Server some additional steps are needed to get your
+OpenVAS installation up and running. This section provides with the information
+you need to generate a server certificate and add users to your installation.
+If you have installed OpenVAS from packages provided by your distribution, be
+aware that there might be differences between the instructions provided by this
+compendium and the steps necessary on your distribution. Please refer to the
+documentation provided by your distribution for additional information.
 \subsection{Generating a Server Certificate}
@@ -1047,7 +1057,7 @@
 Be aware that most of these directories will of course contain files additional
 to the ones described in the following sections; this chapter only points out
-which files will be place by OpenVAS in certain locations.
+which files will be placed by OpenVAS in certain locations.
@@ -1126,8 +1136,8 @@
 OpenVAS-Client is an official Debian package for the distribution "unstable"
 ("Sid) and "testing" ("Lenny"). You can find more information about the Debian
 packages on the OpenVAS-Client package pages
-for Sid\footnote{http://packages.debian.org/sid/openvas-client} and
+for Sid\footnote{\hyperurl{http://packages.debian.org/sid/openvas-client}} and
 This means you can simply install OpenVAS-Client on Debian Sid or Debian
 Lenny with the following command:
@@ -2033,7 +2043,8 @@
 To perform local security checks, you need a working OpenVAS-Server
 installation. Information on setting up and configuring OpenVAS-Server is
-available in chapter \ref{chap:Install-And-Configure-Server}.
+available in chapter \ref{chap:Install-And-Configure-Server} on page
 \subsection{Create users for local security checks}
@@ -2116,7 +2127,7 @@
-\item Install SAMBA (http://www.samba.org)
+\item Install SAMBA (\hyperurl{http://www.samba.org})
 Installation packages should be readily available for your operating system.
@@ -2323,9 +2334,36 @@
-\chapter{Developers Guide for NASL scripts}
+\compendiumauthor{Michael Wiegand}
+The Open Vulnerability and Assessment Language (OVAL) is a standard that can be
+used -- among other things -- to describe known vulnerabilities and tests that
+can be used to assess whether a vulnerability is present on a target system.
+The OVAL community has created ovaldi, an open source reference implementation
+of an OVAL definition interpreter. Although ovaldi initially only supported
+checks of a local system, the OpenVAS project has created a patch that enables
+ovaldi to make use of the information collected by OpenVAS about remote systems.
+Starting from OpenVAS 2.0 beta, ovaldi support is present in OpenVAS. To enable
+ovaldi support, the use of ovaldi in the SVN revision 138 is recommended.
+Please refer to the OpenVAS website for the patch needed for ovaldi and
+up-to-date information regarding ovaldi integration.
+Using ovaldi, you will be able to access hundreds of additional security checks
+provided as definitions in the OVAL standard such as security announcements
+regarding the Red Hat Enterprise Linux distribution. Be aware that the ovaldi
+integration into OpenVAS only supports a limited subset of the tests available
+in OVAL. Support for OVAL tests will be extended as the ovaldi integration
+\chapter{Developers Guide for Network Vulnerability Tests}
 The Network Vulnerability Tests (NVTs) used by OpenVAS to check for existing
 security issues on remote systems are written in the scripting language NASL.
 NASL (short for Nessus Attack Scripting Language) was originally designed for
@@ -2348,6 +2386,14 @@
 programming languages should be able to pick up the basics of NASL development
 in a relatively short amount of time.
+Starting from OpenVAS 2.0 beta, support has been added to OpenVAS for the Open
+Vulnerability and Assessment Language (OVAL) as documented in section
+\ref{sec:ovaldi}. This means that OpenVAS will also understand vulnerability
+tests specified in OVAL. Even though support for OVAL in OpenVAS is very
+limited at this time, you might want to consider OVAL as an alternative when
+writing NVTs. More information about OVAL can be found at
 \section{Basic Structure of NASL Scripts}
@@ -3487,7 +3533,8 @@
 This information should be sufficient to solve the problem. If not, it might be
 an OpenVAS bug in the script engine.
 To detect this, compile OpenVAS NASL with debug symbols and use GDB. More
-information on GBD can be found at: http://www.gnu.org/software/gdb/gdb.html.
+information on GBD can be found at:
 \section{Writing SMBclient-based WLSC NASL Scripts}

More information about the Openvas-commits mailing list