[Openvas-discuss] first post

Javier Fernández-Sanguino Peña jfs at computer.org
Sun Sep 20 11:01:25 CEST 2009

On Fri, Aug 28, 2009 at 11:29:07AM +0200, Felix Wolfsteller wrote:
> Hi John,
> great offer!
> Just came to my mind:
> * Jan mentioned the manpage for openvas-nvt-sync is missing (not really sure 
> if we need one).

I wrote one already yesterday for the Debian package. Please review the
attached file. If it's to everybody's pleasure feel free to commit it to SVN
or ask me to do it.

IMHO I do believe one is needed since people will probably turn to it when
they're having issues downloading updates through rsync


-------------- next part --------------
.\"                                      Hey, EMACS: -*- nroff -*-
.TH OPENVAS-NVT-SYNC 8 "Septmeber 2008" "The OpenVAS Project" "User Manuals"
openvas-nvt-sync \- updates the OpenVAS security checks 
.B openvas-nvt-sync 
.B OpenVAS Security Scanner
performs several security checks, each of them being coded as an external
plugin coded in NASL. As new security holes are published every day, new
plugins appear on the OpenVAS site (www.openvas.org)
The script 
.B openvas-nvt-sync
will fetch all the newest security checks for you and install them at the proper
location. Once this is done you will need to restart openvas-server(8) s
so that it loads them and uses them for new security scans.

.B openvas-nvt-sync
uses rsync(1) and  md5sum(1) to do its job. In order to download the
new plugins the machine where the script runs needs to have
access to rsync.openvas.org using the rsync protocol (TCP/UDP port 873).

If you are behind a web proxy you can configure rsync to use it through the
use of the RSYNC_PROXY environment variable. For more information see

.B openvas-nvt-sync 
uses rsync(1) to retrieve the archive of the new plugins. The scripts
provided by the OpenVAS project might 
.B not be signed
\. Consequently, if somewhere where to poison your DNS server and force this
script to retrieve NASL plugins on another site he would force
your OpenVAS server to execute NASL scripts when running security tests.
Even if this might not do much harm (see the NASL reference guide
for more information on that subject) you should be very careful
when doing this.

For more information see:
.BR rsync(1),
.BR openvasd(8)
.BR openvas-client(1).
There is more information available at
.B /usr/share/doc/openvas-plugins
on Debian systems.
You can find additional information about the OpenVAS project in
This manual page was written by
Javier Fern\['a]ndez-Sanguino Pe\[~n]a <jfs at debian.org>
for the Debian GNU/Linux system (but may be used on other systems).
.B openvas-nvt-sync
script was written by DN-Systems Enterprise Internet Solutions GmbH.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 189 bytes
Desc: Digital signature
URL: <http://lists.wald.intevation.org/pipermail/openvas-discuss/attachments/20090920/7f818d84/attachment.asc>

More information about the Openvas-discuss mailing list