About

OpenVAS
Constitution
OpenVAS-Server
OpenVAS-Client
OpenVAS NVT Feed

Information/Howtos

Integrated tools
Related tools
Security info sources
NVT creation process
Trusted NVTs
Local Security Checks
NVT Feed Services
Articles/Studies
OpenVAS Compendium (en)
OpenVAS Compendium (de)

Support

Bug Tracker

Mailinglist Discussion:
Archive | Subscribe
Mailinglist Announcements:
Archive | Subscribe

Online Chat

Professional Services

Developers Corner

Development Platform
Code quality
Change requests
Internal Architecture
Assigning OIDs for NVTS
Code Documenation

Mailinglist Development:
Archive | Subscribe
Mailinglist Writing NVTs:
Archive | Subscribe
Mailinglist Packaging/Distributing:
Archive | Subscribe
Mailinglist Source Code Commits:
Archive | Subscribe

Download

OpenVAS 2.0:
Server components:
openvas-libraries 2.0.3
openvas-libnasl 2.0.1
openvas-server 2.0.2
openvas-plugins 1.0.7
Client:
openvas-client 2.0.4

OpenVAS 1.0.x:
openvas-libraries 1.0.3
openvas-libnasl 1.0.1
openvas-server 1.0.2
openvas-plugins 1.0.7
OpenVAS-Client 1.0.5

Documentation:
OpenVAS Compendium 1.0.1
PDF (en)
PDF (de)

NVT Lookup by OID

(replace 61039 by any other old-style ID)

OpenVAS Change Request #8: Introduce NVT family "Credentials"

Status: Voted +2. Implemented. Server-side changes released with openvas-plugins 1.0.2, client-side released with OpenVAS-Client 1.0.4.

Purpose

To consistently mark those NVTs that transfer user input on credentials into the knowledge base by setting the family to "Credentials".

References

Initial discussion on openvas-plugins mailing list where this request emerged from.

Rationale

OpenVAS-Client offers a configuration page on "Credentials". It summarizes those "plugin preferences" that are managing parameters for logging in somewhere. OpenVAS-Client identifies them currently by hard-coded names (which is a behavior inherited from Nessus).

Apparently names can change or new ones can appear. It is considered a broken concept to have it necessary to change this in the client application each time such a change occurs. Instead, the client should flexible react on changes happened in OpenVAS server.

Effects

Design and Implementation

History