openvas-libnasl 2.0.2 (2009-08-18)

This is the second maintenance release of the openvas-libnasl module for the
Open Vulnerability Assessment System (OpenVAS) 2.0-series.

It fixes some issues discovered after the release of openvas-libnasl
2.0.1 and introduces support for upcoming features.

Effect when installing this version:
openvas-libnasl 2.0.2 requires openvas-libraries 2.0.4.
Please read effects of the openvas-libraries 2.0.4 release.
The newest OPENVAS_NASL_LEVEL is now 2320, which adds support for
mandatory keys. This feature will be used by NVTs in the future
to improve the scanner performance.

Main changes since 2.0.1:
* Extended the nasl syntax to support 'Mandatory Keys' as part of
  implementation of Change Request #39
  (http://www.openvas.org/openvas-cr-39.html).

Bugfixes:
* Closed bug #911 (http://bugs.openvas.org/911).
  This solved a linker problem related to gcrypt.
* The configure script now remembers its given arguments.

Many thanks to everyone who has contributed to this release: Vlatko Kosturjak,
Matthew Mundell, Jan Wagner, Jan-Oliver Wagner, Michael Wiegand and Felix
Wolfsteller.


openvas-libnasl 2.0.1 (2009-02-12)

This is the first maintenance release of the openvas-libnasl module for the
Open Vulnerability Assessment System (OpenVAS) 2.0-series.

It fixes some issues discovered after the release of openvas-libnasl
2.0.0 and introduces support for upcoming features. Thanks to the continuing
audit of the code, a number of obsolete, unused and/or unnecessary functions
were identified and removed.

Effect when installing this version: openvas-libnasl 2.0.1 requires
openvas-libraries 2.0.1. Please read effects of the openvas-libraries 2.0.1
release.

Main changes since 2.0.0:
* Prepared 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-libnasl/current/index.html

Bugfixes:
* A configuration issue which caused the build process to fail when explicitly
  configured to not build static libraries (--disable-static) has been fixed.
  (Solves: #855)

Many thanks to everyone who has contributed to this release: Tim Brown,
Stjepan Gros, Jan-Oliver Wagner, Felix Wolfsteller and Michael Wiegand.


openvas-libnasl 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:
* Obsolete code relating to the ENABLE_PLUGIN_SERVER macro has been removed.
* The build environment has been harmonized with the rest of OpenVAS.

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 transferring NVT signature information to the client has been
  added.
* New OPENVAS_NASL_LEVEL symbol enabling detection of OpenVAS in plugins.
* Support for new LOG and DEBUG messages.
* New command line parsing for openvas-nasl standalone NASL interpreter.

Many thanks to everyone who has contributed to this release: Tim Brown, Stjepan
Gros, Jan Wagner, Jan-Oliver Wagner, Michael Wiegand and Felix Wolfsteller.


openvas-libnasl 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.
* Minor bugfixes.

Many thanks to everyone who has contributed to this release: Tim Brown and
Michael Wiegand.


openvas-libnasl 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, 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 transferring NVT signature information to the client has been added.
* Bugfixes.
* Various code cleanups.

Many thanks to everyone who has contributed to this release: Tim Brown, Stjepan
Gros, Michael Wiegand and Felix Wolfsteller.


openvas-libnasl 2.0-beta1 (2008-09-24)

This release is a first beta version of the upcoming 2.0 release of OpenVAS.
This release adds support for OpenVAS detection in plugins and introduce two
new NASL functions to support the new LOG and DEBUG message type. These
message types can be sent from within NASL using the log_message() and
debug_message() commands. In addition, this release contains updated packaging
files for Debian and completely rewritten command line parsing functionality
for the openvas-nasl tool.

OpenVAS 2.0 will introduce a full set of new modules for OpenVAS Server
(openvas-libraries, openvas-libnasl and openvas-server) and the 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:
* Updates of Debian packaging files.
* New OPENVAS_NASL_LEVEL symbol enabling detection of OpenVAS in plugins.
* Support for new LOG and DEBUG messages.
* New command line parsing for openvas-nasl standalone NASL interpreter.

Many thanks to everyone who has contributed to this release: Tim Brown, Jan
Wagner, Jan-Oliver Wagner and Michael Wiegand

openvas-libnasl 1.0.1 (2008-07-01)

This release contains changes to the packaging files for various distributions
as well as minor bug fixes, cleanups and copyright clarifications.
Apart from this, this release prepares OID support for OpenVAS.

Please note that this version requires openvas-libraries 1.0.2 or newer.

* Changed version requirements for gpgme from 1.1.5 to 1.1.2; 1.1.2 is the 
  default version in Debian Etch and already contains sufficient functionality.
* Added packaging files for Debian, OpenSUSE and Fedora.
* Preparation for support for OpenVAS OIDs.
* Changed version requirements for openvas-libraries from 0.9.2 to 1.0.2 due to
  API extension for OpenVAS OIDs.
* Removed proprietary NASL2 reference.
* Fixed a configuration issue that broke the build process on certain 64bit
  installations.
* Improved copyright information, various copyright clarifications.
* Various code cleanups.

openvas-libnasl 1.0.0 (2008-01-04)

First stable release with only minimal changes
compared to latest 0.9 version.
No other problems have been reported for over
two months now. This release is done basically
to reach the mentally important version 1.0,
there is no technical need to replace openvas-libnasl
for a running installation.

Main changes are:

* configure: improved check for gpgme version
* Minor code cleanups

openvas-libnasl 0.9.2 (2007-11-01)

Bug-fix release making local security checks work.

Main changes are:

* Internal fixes to enable pkcs8 rsa keys to be used
  for local security checks, i.e. to login via ssh.
* Fixed Makefile cleanup process.
* Minor fixes in documentation.

openvas-libnasl 0.9.1 (2007-10-15)

Introducing GnuPG detached signature(s) support.

Main changes are:

* Now tests for minimum required version of openvas-libraries during configure.
* Missing signatures are now treated like bad signatures.
* Removed "-S" option for signing a plugin from "nasl" command.
* Support of checking detached GnuPG signatures for .nasl files.
* Extended test suite for signature verification.
* Added gpgme (the crypto interface library for GnuPG) as required dependency.
* Removed installation of nessus_org.pem.
* Introduced version handling of its own for openvas-libnasl.
* Fixed paths for state_dir.
* Switched on all compiler warnings during build by default.
* Various compiler warning resolved.
* Various code cleanups.

openvas-libnasl 0.9.0 (2007-07-27)

The first initial release of openvas-libnasl
after the fork from Nessus 2.2.x.

Main changes are:

* Replace OpenSSL by GNU/TLS (therefore it is allowed now to distribute
  binary packages with SSL-support)
* SSL now mandatory.
* Many cleanups of ancient remains (still many to come)
* Removed various W32-specific elements, because W32 isn't
  a taget system anyway.
* Lots of renaming to avoid conflicts with parallel
  Nessus installation
