[Openvas-devel] Get rid of old services concept

Chandrashekhar B bchandra at secpod.com
Mon Sep 7 15:28:08 CEST 2009


-----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: Sunday, September 06, 2009 2:36 PM
To: openvas-devel at wald.intevation.org
Subject: [Openvas-devel] Get rid of old services concept


> * It is questionalbel whether it makes sense at all
>   to maintain services database on out own at all.
>   In case we would do it, the only sensible way
>   is to distribute it over the feed so it is always
>   uptodate.

Maintaining on our own, you mean, distributing through openvas-nvt-sync? I
think it should only be distribution and there's no maintenance.

>* What we might really want is to share effords
>   with the nmap people. Distributuing the newes
>   data via the feed remains still an option here.

> What to do?

> IMHO, we should drop the whole services code
> stuff and use the glibc API using a thin layer
> that allows us to go for a nmap database
> distributed via feed.

I agree. NMAP is the way to go.

Thanks,
Chandra.




More information about the Openvas-devel mailing list