[Openvas-devel] Preparing OpenVAS 3.0: features and timeline
Jan-Oliver.Wagner at greenbone.net
Wed Sep 9 10:26:26 CEST 2009
I'd like to stress that the renaming should really be done
for the sake of consistent and easy to understand wording.
On Thursday 03 September 2009 15:24:27 Jan-Oliver Wagner wrote:
> 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.
Ideally we should end up with:
openvas-scanner, opernvas-manager, openvas-administrator,
openvas-client and openvas-libraries.
Daemon names: openvassd, openvasmd, openvasad
Protocol names: OSP (OpenVAS Scanner Protocol,
a yet to be designed protocol that is in line with
the design of OMP), OMP (OpenVAS Manager Protocol)
and OAP (OpenVAS Administrator Protocol).
Please let us know if you agree, don't agree with this
or like to add thoughts.
Dr. Jan-Oliver Wagner | ++49-541-335084-0 | http://www.greenbone.net/
Greenbone Networks GmbH, Neuer Graben 17, 49074 Osnabrück
AG Osnabrück, HR B 202460 | Geschäftsführer: Lukas Grunwald, Dr. Jan-Oliver Wagner
More information about the Openvas-devel