Commit 068737f7 authored by Lock Lin's avatar Lock Lin

Import Upstream version 3.0.2

parents
openvas-scanner 3.0.2 (2010-03-22)
This is the second maintenance release of the openvas-scanner module for the
Open Vulnerability Assessment System (OpenVAS) 3.0-series.
This release mainly improves the supporting shell scripts for
user- and feed-management.
Many thanks to everyone who has contributed to this release:
Javier Fernandez-Sanguino, Stephan Kleine, Michael Meyer,
Jan-Oliver Wagner, Michael Wiegand and Felix Wolfsteller.
Main changes compared to 3.0.1:
* Changed C-NVT "find_service" to mark unknown services.
* Improved script "openvas-adduser" regarding exit code.
* Improved script "openvas-mkcert-client" to allow clean
certificate creation and to allow non-interactive execution.
* Improved script "openvas-nvt-sync" to comply with openvas-adminstrator
API specification of NVT sync scripts. Also more robustness.
* Added script "greenbone-nvt-sync".
* Small internal code cleanups.
openvas-scanner 3.0.1 (2010-01-26)
This is the first maintenance release of the openvas-scanner module for the
Open Vulnerability Assessment System (OpenVAS) 3.0-series.
It reenables certificate authentication, improves user rules support and
includes an updated openvas-nvt-sync script.
Many thanks to everyone who has contributed to this release:
Vlatko Kosturjak, Matthew Mundell, Jan-Oliver Wagner, Michael Wiegand and Felix
Wolfsteller.
Main changes compared to 3.0.0:
* Reenabled certificate authentication
* Improved user rules support
* Updated openvas-nvt-sync script
openvas-scanner 3.0.0 (2009-12-18)
This is the 3.0.0 release of the openvas-scanner module for the Open
Vulnerability Assessment System (OpenVAS). Apart from the name change
from openvas-server to openvas-scanner, now the platform-dependent NVTs
as well as the OpenVAS NVT Feed synchronisation script have been
integrated.
OpenVAS 3.0 introduces a new architecture where openvas-libraries now
includes openvas-libnasl as well as redundant code from openvas-client
and where openvas-server is renamed to openvas-scanner and includes any
platform-dependent elements of openvas-plugins. As a result of this, the
source code line count has been reduced even though new features have
been added. Also, for running the scanner now only 2 modules are
required (instead of 4 as for OpenVAS 2.0).
New features of OpenVAS include support for IPv6 and WMI-Clients.
Version 3.0 also supports the new OpenVAS Manager and OpenVAS
Administrator as optional extensions. This combination leverages the
vulnerability scanner to a comprehensive vulnerability management
solution.
Many thanks to everyone who has contributed to the 3.0.0 release:
Chandrashekhar B, Tim Brown, Javier Fernández-Sanguino Peña, Vlatko
Kosturjak, Matthew Mundell, Srinivasa NL, Jan Wagner, Jan-Oliver Wagner,
Michael Wiegand and Felix Wolfsteller.
Main changes compared to 2.0.x:
* IPv6 support
* Integration of platform dependent NVTs from openvas-plugins
* Integration of openvas-nvt-sync script
* Renamed daemon from openvasd to openvassd
* glib dependency raised from 2.6 to 2.12
* openvasd-config removed as no other packages require this package for
building.
* For the same reason, no header files are installed anymore
Main changes compared to 3.0.0-rc1:
* The openvassd.conf configuration file now complies with the key file
specification.
openvas-scanner 3.0.0-rc1 (2009-12-07)
This release is the first release candidate of openvas-scanner
leading up to the upcoming 3.0 release of OpenVAS.
Apart from the name change from openvas-server to
openvas-scanner, the platform-dependent NVTs as
well as the OpenVAS NVT Feed synchronisation script
are now integrated.
OpenVAS 3.0 will introduce a new architecture where openvas-libraries
now includes openvas-libnasl as well as redundant code from openvas-client
and where openvas-server is renamed to openvas-scanner and includes any
platform-dependent elements of openvas-plugins. As a result of this,
the source code will shrink, though new features will be added. Also,
for running the scanner now only 2 modules are required (instead of 4
as for OpenVAS 2.0).
New features of OpenVAS include support for IPv6 and WMI-Clients.
Version 3.0 prepares the new OpenVAS Manager and OpenVAS Administrator
as optional extension. This combination leverages the vulnerability
scanner to a comprehensive vulnerability management solution.
The "release candidate" releases are intended to allow testing of the upcoming
3.0 series. It should be kept separate from OpenVAS 2.0 installations
and not be used in a production environment.
Unless serious bugs are discovered, this release candidate will become the final
OpenVAS 3.0 release. Users are encouraged to test this release and to report
bugs to the OpenVAS bug tracker located at http://bugs.openvas.org/ .
Many thanks to everyone who has contributed to the 3.0.0 release:
Chandrashekhar B, Tim Brown, Javier Fernández-Sanguino Peña,
Vlatko Kosturjak, Matthew Mundell, Srinivasa NL, Jan Wagner,
Jan-Oliver Wagner, Michael Wiegand and Felix Wolfsteller.
Main changes compared to 2.0.x:
* IPv6 support
* Integration of platform dependent NVTs from openvas-plugins
* Integration of openvas-nvt-sync script
* Renamed daemon from openvasd to openvassd
* glib dependency raised from 2.6 to 2.12
* openvasd-config removed as no other packages require this
package for building.
* For the same reason, no header files are installed anymore
Main changes compared to 3.0.0-beta6:
* IPv6 support has been improved.
* Support for the upcoming synchronization script API has been added to
openvas-nvt-sync.
* The amount of debug messages in the log files when not compiled in debug
mode has been reduced.
openvas-scanner 3.0.0-beta6 (2009-11-23)
This release is the sixth beta version of openvas-scanner
leading up to the upcoming 3.0 release of OpenVAS.
Apart from the name change from openvas-server to
openvas-scanner, the platform-dependent NVTs as
well as the OpenVAS NVT Feed synchronisation script
are now integrated.
OpenVAS 3.0 will introduce a new architecture where openvas-libraries
now includes openvas-libnasl as well as redundant code from openvas-client
and where openvas-server is renamed to openvas-scanner and includes any
platform-dependent elements of openvas-plugins. As a result of this,
the source code will shrink, though new features will be added. Also,
for running the scanner now only 2 modules are required (instead of 4
as for OpenVAS 2.0).
New features of OpenVAS include support for IPv6 and WMI-Clients.
Version 3.0 prepares the new OpenVAS Manager and OpenVAS Administrator
as optional extension. This combination leverages the vulnerability
scanner to a comprehensive vulnerability management solution.
The "beta" releases are intended to allow testing of the upcoming
3.0 series. It should be kept separate from OpenVAS 2.0 installations
and not be used in a production environment.
Many thanks to everyone who has contributed to the 3.0.0 release:
Chandrashekhar B, Tim Brown, Javier Fernández-Sanguino Peña,
Vlatko Kosturjak, Matthew Mundell, Srinivasa NL, Jan Wagner,
Jan-Oliver Wagner, Michael Wiegand and Felix Wolfsteller.
Main changes compared to 2.0.x:
* IPv6 support
* Integration of platform dependent NVTs from openvas-plugins
* Integration of openvas-nvt-sync script
* Renamed daemon from openvasd to openvassd
* glib dependency raised from 2.6 to 2.12
* openvasd-config removed as no other packages require this
package for building.
* For the same reason, no header files are installed anymore
Main changes compared to 3.0.0-beta5:
* IPv6 support has been improved.
* Code clean up.
openvas-scanner 3.0.0-beta5 (2009-10-26)
This release is the fifth beta version of openvas-scanner
leading up to the upcoming 3.0 release of OpenVAS.
Apart from the name change from openvas-server to
openvas-scanner, the platform-dependent NVTs as
well as the OpenVAS NVT Feed synchronisation script
are now integrated.
OpenVAS 3.0 will introduce a new architecture where openvas-libraries
now includes openvas-libnasl as well as redundant code from openvas-client
and where openvas-server is renamed to openvas-scanner and includes any
platform-dependent elements of openvas-plugins. As a result of this,
the source code will shrink, though new features will be added. Also,
for running the scanner now only 2 modules are required (instead of 4
as for OpenVAS 2.0).
New features of OpenVAS include support for IPv6 and WMI-Clients.
Version 3.0 prepares the new OpenVAS Manager and OpenVAS Administrator
as optional extension. This combination leverages the vulnerability
scanner to a comprehensive vulnerability management solution.
The "beta" releases are intended to allow testing of the upcoming
3.0 series. It should be kept separate from OpenVAS 2.0 installations
and not be used in a production environment.
Many thanks to everyone who has contributed to the 3.0.0 release:
Chandrashekhar B, Tim Brown, Javier Fernández-Sanguino Peña,
Vlatko Kosturjak, Matthew Mundell, Srinivasa NL, Jan Wagner,
Jan-Oliver Wagner, Michael Wiegand and Felix Wolfsteller.
Main changes compared to 2.0.x:
* IPv6 support
* Integration of platform dependent NVTs from openvas-plugins
* Integration of openvas-nvt-sync script
* Renamed daemon from openvasd to openvassd
* glib dependency raised from 2.6 to 2.12
* openvasd-config removed as no other packages require this
package for building.
* For the same reason, no header files are installed anymore
Main changes compared to 3.0.0-beta4:
* Adjustments for the API changes that happened from
openvas-libraries 3.0.0-beta4 to 3.0.0-beta5.
openvas-scanner 3.0.0-beta4 (2009-10-19)
This release is the fourth beta version of openvas-scanner
leading up to the upcoming 3.0 release of OpenVAS.
Apart from the name change from openvas-server to
openvas-scanner, the platform-dependent NVTs as
well as the OpenVAS NVT Feed synchronisation script
are now integrated.
OpenVAS 3.0 will introduce a new architecture where openvas-libraries
now includes openvas-libnasl as well as redundant code from openvas-client
and where openvas-server is renamed to openvas-scanner and includes any
platform-dependent elements of openvas-plugins. As a result of this,
the source code will shrink, though new features will be added. Also,
for running the scanner now only 2 modules are required (instead of 4
as for OpenVAS 2.0).
New features of OpenVAS include support for IPv6 and WMI-Clients.
Version 3.0 prepares the new OpenVAS Manager and OpenVAS Administrator
as optional extension. This combination leverages the vulnerability
scanner to a comprehensive vulnerability management solution.
The "beta" releases are intended to allow testing of the upcoming
3.0 series. It should be kept separate from OpenVAS 2.0 installations
and not be used in a production environment.
Many thanks to everyone who has contributed to the 3.0.0 release:
Chandrashekhar B, Tim Brown, Javier Fernández-Sanguino Peña,
Vlatko Kosturjak, Matthew Mundell, Srinivasa NL, Jan Wagner,
Jan-Oliver Wagner, Michael Wiegand and Felix Wolfsteller.
Main changes compared to 2.0.x:
* IPv6 support
* Integration of platform dependent NVTs from openvas-plugins
* Integration of openvas-nvt-sync script
* Renamed daemon from openvasd to openvassd
* glib dependency raised from 2.6 to 2.12
* openvasd-config removed as no other packages require this
package for building.
* For the same reason, no header files are installed anymore
Main changes compared to 3.0.0-beta3:
* A number of resource and memory leaks have been identified and fixed.
* Command line options have been updated.
* Old and obsolete code has been identified and removed.
* Adjustments for the API changes that happened from
openvas-libraries 3.0.0-beta3 to 3.0.0-beta4.
openvas-scanner 3.0.0-beta3 (2009-10-06)
This release is the third beta version of openvas-scanner
leading up to the upcoming 3.0 release of OpenVAS.
Apart from the name change from openvas-server to
openvas-scanner, the platform-dependent NVTs as
well as the OpenVAS NVT Feed synchronisation script
are now integrated.
OpenVAS 3.0 will introduce a new architecture where openvas-libraries
now includes openvas-libnasl as well as redundant code from openvas-client
and where openvas-server is renamed to openvas-scanner and includes any
platform-dependent elements of openvas-plugins. As a result of this,
the source code will shrink, though new features will be added. Also,
for running the scanner now only 2 modules are required (instead of 4
as for OpenVAS 2.0).
New features of OpenVAS include support for IPv6 and WMI-Clients.
Version 3.0 prepares the new OpenVAS Manager and OpenVAS Administrator
as optional extension. This combination leverages the vulnerability
scanner to a comprehensive vulnerability management solution.
The "beta" releases are intended to allow testing of the upcoming
3.0 series. It should be kept separate from OpenVAS 2.0 installations
and not be used in a production environment.
Many thanks to everyone who has contributed to the 3.0.0 release:
Chandrashekhar B, Tim Brown, Javier Fernández-Sanguino Peña,
Vlatko Kosturjak, Matthew Mundell, Srinivasa NL, Jan Wagner,
Jan-Oliver Wagner, Michael Wiegand and Felix Wolfsteller.
Main changes compared to 2.0.x:
* IPv6 support
* Integration of platform dependent NVTs from openvas-plugins
* Integration of openvas-nvt-sync script
* Renamed daemon from openvasd to openvassd
* glib dependency raised from 2.6 to 2.12
* openvasd-config removed as no other packages require this
package for building.
* For the same reason, no header files are installed anymore
Main changes compared to 3.0.0-beta2:
* Adjustments for the API changes that happened from
openvas-libraries 3.0.0-beta2 to 3.0.0-beta3.
openvas-scanner 3.0.0-beta2 (2009-09-28)
This release is the second beta version of openvas-scanner
leading up to the upcoming 3.0 release of OpenVAS.
Apart from the name change from openvas-server to
openvas-scanner, the platform-dependent NVTs as
well as the OpenVAS NVT Feed synchronisation script
are now integrated.
OpenVAS 3.0 will introduce a new architecture where openvas-libraries
now includes openvas-libnasl as well as redundant code from openvas-client
and where openvas-server is renamed to openvas-scanner and includes any
platform-dependent elements of openvas-plugins. As a result of this,
the source code will shrink, though new features will be added. Also,
for running the scanner now only 2 modules are required (instead of 4
as for OpenVAS 2.0).
New features of OpenVAS include support for IPv6 and WMI-Clients.
Version 3.0 prepares the new OpenVAS Manager and OpenVAS Administrator
as optional extension. This combination leverages the vulnerability
scanner to a comprehensive vulnerability management solution.
The "beta" releases are intented to allow testing of the upcoming
3.0 series. It should be kept separate from OpenVAS 2.0 installations
and not be used in a production environment.
Many thanks to everyone who has contributed to the 3.0.0 release:
Chandrashekhar B, Tim Brown, Javier Fernández-Sanguino Peña,
Vlatko Kosturjak, Matthew Mundell, Srinivasa NL, Jan Wagner,
Jan-Oliver Wagner, Michael Wiegand and Felix Wolfsteller.
Main changes compared to 2.0.x:
* IPv6 support
* Integration of platform dependent NVTs from openvas-plugins
* Integration of openvas-nvt-sync script
* Renamed daemon from openvasd to openvassd
* glib dependency raised from 2.6 to 2.12
* openvasd-config removed as no other packages require this
package for building.
* For the same reason, no header files are installed anymore
Main changes compared to 3.0.0-beta1:
* Adjustments for the API changes that happened from
openvas-libraries 3.0.0-beta1 to 3.0.0-beta2.
* Code cleanups.
* Fixed and improved build.
openvas-scanner 3.0.0-beta1 (2009-09-23)
This release is the first beta version of openvas-scanner
leading up to the upcoming 3.0 release of OpenVAS.
Apart from the name change from openvas-server to
openvas-scanner, and platform-dependent NTSs as
well as the OpenVAS NVT Feed synchronisation script
are now integrated.
OpenVAS 3.0 will introduce a new architecture where openvas-libraries
now includes openvas-libnasl as well as redundant code from openvas-client
and where openvas-server is renamed to openvas-scanner and includes any
platform-dependent elements of openvas-plugins. As a result of this,
the source code will shrink, though new features will be added. Also,
for running the scanner now only 2 modules are required (instead of 4
as for OpenVAS 2.0).
New features of OpenVAS include support for IPv6 and WMI-Clients.
Version 3.0 prepares the new OpenVAS Manager and OpenVAS Administrator
as optional extension. This combination leverages the vulnerability
scanner to a comprehensive vulnerability management solution.
The "beta" releases are intented to allow testing of the upcoming
3.0 series. It should be kept separate from OpenVAS 2.0 installations
and not be used in a production environment.
Many thanks to everyone who has contributed to the 3.0.0 release:
Chandrashekhar B, Tim Brown, Javier Fernández-Sanguino Peña,
Vlatko Kosturjak, Matthew Mundell, Srinivasa NL, Jan Wagner,
Jan-Oliver Wagner, Michael Wiegand and Felix Wolfsteller.
Main changes compared to 2.0.x:
* IPv6 support
* Integration of platform dependent NVTs from openvas-plugins
* Integration of openvas-nvt-sync script
* Renamed daemon from openvasd to openvassd
* glib dependency raised from 2.6 to 2.12
* openvasd-config removed as no other packages require this
package for building.
* For the same reason, no header files are installed anymore
openvas-server 2.0.2 (2009-06-03)
This is the second maintenance release of the openvas-server module for the
Open Vulnerability Assessment System (OpenVAS) 2.0-series.
It fixes some issues discovered after the release of openvas-server
2.0.1 and introduces support for new features. Thanks to the continuing
audit of the code, a number of obsolete, unused and/or unnecessary functions
were identified and removed.
Effects when installing this version:
* The option "Silent dependencies" is now "off" by default. Previously it was
set to "on", openvas-client >= 2.0.2 has already switched to "off" per
default. Note that this may result in larger reports.
* Dependencies: openvas-server 2.0.2 requires openvas-libraries 2.0.2 and
openvas-libnasl 2.0.1. You need to install these prior to openvas-server 2.0.2.
* The openvas-adduser script will no longer allow passwords in plaintext for new
users. This means that the openvas-adduser script will refuse to add a new
user if neither openssl nor md5sums is available.
Main changes since 2.0.1:
* OVAL support has been improved and now supports multiple definitions and
results in one file.
* Support for per-host password based local checks has been added.
* Debian packaging files have been updated.
* Dependency searching has been improved to work better with subdirectories.
* openvas-server will now generate a warning if a NVT could not be cached.
* The openvas-adduser script will no longer create the now obsolete "plugins"
directory in the user directory.
Many thanks to everyone who has contributed to this release: Vlatko Kosturjak,
Jan Wagner, Felix Wolfsteller and Michael Wiegand.
openvas-server 2.0.1 (2009-02-17)
This is the first maintenance release of the openvas-server module for the
Open Vulnerability Assessment System (OpenVAS) 2.0-series.
It fixes some issues discovered after the release of openvas-server
2.0.0 and introduces support for new features. Thanks to the continuing
audit of the code, a number of obsolete, unused and/or unnecessary functions
were identified and removed.
Effects when installing this version:
* Dependencies: openvas-server 2.0.1 requires openvas-libraries 2.0.1 and
openvas-libnasl 2.0.1. You need to install these prior to openvas-server 2.0.1.
* Cache files: Effects of openvas-libraries 2.0.1 are changes in the
cache file management. With 2.0.1 release of openvas-server it is
possible to specify a new location for the cache folder. If you will
use a new location, then the effects described for openvas-libraries
do not apply anymore (see also below regarding cache folder).
* New default port of the server: Please be aware that openvas-server
now listens on port 9390 by default since this port has recently been allocated
by IANA for the Openvas Transport Protocol (OTP). If you want to continue to
use the old port 1241, you have to specify the port you want openvasd to
listen on, for example by starting the server with "openvasd -p 1241".
If you don't specify this, it might happen that at next boot of your
system (or other restart of openvasd), the service is available
at a new port and you need to update the connection information
in your OpenVAS-Client.
Main changes since 2.0.0:
* Support for sub-directories in plugins_folder in accordance with
Change Request #24 (http://www.openvas.org/openvas-cr-24.html).
* Established automated source code documentation. HTML-Version is available
under http://www.openvas.org/src-doc/openvas-server/current/index.html
* Openvas-server now uses the IANA-assigned port 9390 for communication
with the client.
* It is now possible to start openvas-server without root privileges. Note that
a number of NVTs which rely on operations requiring root privileges (like
packet forgery) will not work under these circumstances.
* The openvasd-config script now returns the values for sysconfdir, libdir and
sbindir set at compile time.
* The new server preference "cache_folder" allows you to define the location
of the cache ($plugins_folder/.desc in previous versions). The default value
for this preference is /var/cache/openvas for new OpenVAS installations.
Existing installations need to add cache_folder = /var/cache/openvas
manually to openvasd.conf and make sure the directory exists.
* The new server preference "include_folders" allows you to specify
search paths for the NASL include directive. This aids the use of
subdirectories for plugins. The default value for this preference is
$plugins_folder to be compatible with the old "flat" (all in one directory)
structure.
* Initial support for per-target SSH credentials settings has been added. Please
note that you will need a new client (>= 2.0.2) and a new ssh_authorization.nasl file to
use this feature.
* Having a directory structure in $plugins_folder is now supported. openvasd
will recurse through the subdirectories in $plugins_folder.
Note: The OpenVAS NVT feed will not use the new features for subdirectories and
include paths as long as the OpenVAS 1.0.x and OpenVAS 2.0.0 releases are
supported. An exception might be OVAL support.
Bugfixes:
* The usage of the gettext support tool in support scripts like openvas-adduser
did expect gettext.sh to be in /usr/bin, which prevented the scripts from
working correctly on systems where this was not the case. The gettext usage
has been made more robust. (Solves: #860)
* During startup, openvasd will now show the correct total number of plugins
and not count signatures and other files anymore.
* The obsolete user-specific cache (.desc in
/var/lib/openvas/users/USER/plugins/) is not created anymore.
Many thanks to everyone who has contributed to this release: Tim Brown,
Stjepan Gros (for subdirs feature), Joey Schulze, Jan-Oliver Wagner,
Felix Wolfsteller and Michael Wiegand.
openvas-server 2.0.0 (2008-12-17)
This is the 2.0.0 release of OpenVAS.
If you have used the 2.0-beta1, -beta2 or -rc1 release, we recommend that you
update all your OpenVAS modules (openvas-libraries, openvas-libnasl,
openvas-server and openvas-client) to 2.0.0.
If you are currently using the 1.0.x branch and want to evaluate OpenVAS
2.0.0, we recommend that you install 2.0.0 separately from your OpenVAS 1.0
installation. Instructions on how to do this are available from the OpenVAS
website.
Main changes since 2.0-rc1:
* Debian packaging files have been updated.
* Obsolete code relating to the ENABLE_PLUGIN_SERVER has been removed.
* The build environment has been updated.
Main changes since 1.0.1:
* Support for the new script_tag command in NASL scripts has been added.
* 64-bit compatibility has been considerably improved.
* Support for transfering NVT signature information to the client has been added.
* Certificate checking has been improved.
* The obsolete openvas-check-signature tool has been removed.
* Support for plugin upload has been removed from OpenVAS-Server.
* Support for detached scans has been removed from OpenVAS-Server.
* Switch from Nessus Transfer Protocol 1.2 to OpenVAS Transfer Protocol (OTP) 1.0.
* Support for OVAL definitions has been added.
* Switch from Nessus plugin IDs to NVT OIDs.
Many thanks to everyone who has contributed to this release: Tim Brown, Javier
Fernandez-Sanguino, Stjepan Gros, Joey Schulze, Jan Wagner, Jan-Oliver Wagner,
Michael Wiegand and Felix Wolfsteller.
openvas-server 2.0-rc1 (2008-12-05)
This release is the first release candidate for the upcoming 2.0 release of OpenVAS.
Unless serious bugs are discovered, this release candidate will become the final
OpenVAS 2.0 release. Users are encouraged to test this release and to report
bugs to the OpenVAS bug tracker located at http://bugs.openvas.org/ .
If you have used the 2.0-beta2 release, we recommend that you update all your
OpenVAS modules (openvas-libraries, openvas-libnasl, openvas-server and
openvas-client) to 2.0-rc1.
If you are currently using the stable 1.0.x branch and want to take part in
testing this release candidate, we recommend that you install 2.0-rc1 separately
from your OpenVAS 1.0 installation. Instructions on how to do this are available
from the OpenVAS website.
Main changes since 2.0-beta2:
* Support for the new script_tag command in NASL scripts has been added.
* Code quality has been improved, a potential buffer overflow due to
insufficient memory allocation has been fixed.
* Debian packaging files have been updated.
* Minor bugfixes.
Many thanks to everyone who has contributed to this release: Tim Brown, Joey
Schulze, Felix Wolfsteller and Michael Wiegand.
openvas-server 2.0-beta2 (2008-11-14)
This release is the second beta version of the upcoming 2.0 release of OpenVAS.
It contains improved 64-bit compatibility, improved OVAL support, support for
transferring NVT signature information to the client and various improvements.
This release is intended to contain all features intended for the final OpenVAS
2.0 release. Users are encouraged to test this release and to report bugs to the
OpenVAS bug tracker located at http://bugs.openvas.org/ .
If you have used the 2.0-beta1 release, we recommend that you update all your
OpenVAS modules (openvas-libraries, openvas-libnasl, openvas-server and
openvas-client) to 2.0-beta2.
If you are currently using the stable 1.0.x branch and want to take part in the
beta phase for 2.0, we recommend that you install 2.0-beta2 separately from your
OpenVAS 1.0 installation. Instructions on how to do this are available from the
OpenVAS website.
Main changes since 2.0-beta1:
* 64-bit compatibility has been considerably improved.
* Debian packaging files have been updated.
* Support for transfering NVT signature information to the client has been added.
* Certificate checking has been improved.
* OVAL support has been improved.
* The obsolete openvas-check-signature tool has been removed.
* Bugfixes.
* Various code cleanups.
Many thanks to everyone who has contributed to this release: Tim Brown, Stjepan
Gros, Michael Wiegand and Felix Wolfsteller.
openvas-server 2.0-beta1 (2008-09-25)
This release is a first beta version of the upcoming 2.0 release of OpenVAS.
It introduces support for the cleaned up and improved OpenVAS Transport Protocol
(OTP, replacing NTP), the new OpenVAS NVT OID scheme and support for the Open
Vulnerability and Assessment Language (OVAL).
The protocol cleanup also removed some features that were considered unsecure,
unneeded or wrongly placed.
OpenVAS 2.0 will introduce a full set of new modules for OpenVAS Server
(openvas-libraries, openvas-libnasl and openvas-server) and a new
OpenVAS-Client. The only module OpenVAS 1.0 and OpenVAS 2.0 will share is
openvas-plugins. This means that the OpenVAS NVT Feed is compatible with both
generations of OpenVAS.
However, in case you plan to try out the new generation of OpenVAS, you should
install it separately from OpenVAS 1.0 installation. Instructions on how to do
this will be added to the OpenVAS homepage after all relevant modules are
released as 2.0-beta1. A separate announcement will officially start the beta
testing phase for OpenVAS 2.0.
Main changes in this release (compared to release 1.0.1):
* Updated packaging files for Debian.
* Support for plugin upload has been removed from OpenVAS-Server.