[Openvas-devel] Preparing OpenVAS 3.0: features and timeline

Christian Eric Edjenguele christian.edjenguele at owasp.org
Mon Sep 7 16:24:53 CEST 2009


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Chandrashekhar B wrote:
> I have two items in my agenda, to write CR's for,
> - Description separation from the code in NVT's

This is a prety good idea, in fact it should be great to keep
description out of code, maybe in in some database. This could also
solve some problems such as duplicate script_id, using an auto-increment
based on user commits.

> - SMB library integration for SMB/DCERPC packet crafting.
> 
> This can go for 3.0 or may be for later releases.
> 
> Thanks,
> Chandra. 
> 
> -----Original Message-----
> From: openvas-devel-bounces at wald.intevation.org
> [mailto:openvas-devel-bounces at wald.intevation.org] On Behalf Of Jan-Oliver
> Wagner
> Sent: Thursday, September 03, 2009 6:54 PM
> To: openvas-devel at wald.intevation.org
> Subject: [Openvas-devel] Preparing OpenVAS 3.0: features and timeline
> 
> Hi,
> 
> it is getting time to bring OpenVAS on the track to 3.0.
> 
> First of all: I was initially thinking that we will have a 2.1 release
> first. However, IMHO the significant changes in architecture
> and features justify a 3.0.
> 
> Main idea:
> OpenVAS 3.0 introduce various new features and
> a improved internal architcture. But it should not make
> OpenVAS-Manager mandatory yet. It rather should
> recommend to try out OpenVAS-Manager, because
> it will be supported well by OpenVAS 3.0.
> OpenVAS 4.0 should then have OpenVAS-Manager
> as mandatory default (while OTP is still being supported).
> OpenVAS 5.0 should not support OTP anymore - OMP 
> is the protocol every client uses.
> 
> New Features and changes in OpenVAS 3.0:
> 
> * Drop module openvas-libnasl (done)
> * Drop module openvas-plugins (done)
> * IPv6 Support (in progress)
> * WMI-client support (done)
> * OpenVAS-Client depends on openvas-libraries (done)
> * OpenVAS-Client supports OMP (in progress)
> * OpenVAS-Client migrates from OpenSSL to GNU/TLS (in progress)
> * OpenVAS-Client offer command line client for OMP (in progress)
> * OpenVAS-Client compiles for Windows (in progress)
> * OpenVAS-Server uses new NVT cache (faster, no size limits for NVTs in the
> future)
> 
> What I like to change for 3.0 also:
> 
> * rename openvasd to openvassd for scan daemon.
>   This would be in line with openvasmd (manager daemon)
>   and openvascd (configuration daemon)
> 
> * In fact, rename "openvas-server" to "openvas-scanner"
>    because "server" is a bit too generic.
> 
> * new rules file format. The rules are really badly managed.
> 
> * new openvas(s)d.conf format: use keyfile here.
> 
> Timeline:
> 
> Have 3.0.0beta1 in October.
> Have 3.0.0 before Christmas.
> 
> 
> Please feel free to add things I forgot or you would like to add.
> Any other comments welcome as well.
> Perhaps we can generate some CRs out of this discussion.
> 
> Anyone volunteering to create a nice roadmap webpage?
> (http://www.openvas.org/roadmap.html is a bit, well ... thin)
> 
> All the best
> 
> 	Jan
> 


- --
Christian Eric Edjenguele
IT Security Engineer
PGP KeyID: 0xB1654498

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iQEcBAEBAgAGBQJKpRetAAoJENETScWxZUSYGGQIAIp52waLcfKG+2lYRbOHZ8+5
/kzn+dFuDrGoA+f+ic0yH6sH8wJrPMTOVm+lbSnjeiZo/3zr9j9r+KcCDafhdm/p
eZPxb/7XzUEbeADXYW6WRbMvkMrfqGDErNHhWSYpznmYeTCOTepipHzIYL1je7vG
U0UrX4Mb6weUfY9VT3P+O2eRz4GPxbykhUNrBm2/O2OI1ofRQl6VMCBQUmR3St4P
fzo7HgMNVVPiTcQZNJVOQ/y5bO7QXDh15mfNcyppdxfyKZx9YmrvwaMcr2rv5cr0
jG8bTqM7DUYFkh8N4RxhDENMNl3cJbyfGjzGmpjZjvjWj9zwB/u7oDb+a+0K9wM=
=EFGs
-----END PGP SIGNATURE-----


More information about the Openvas-devel mailing list