On Freitag, 29. August 2008, Jan-Oliver Wagner wrote:
> On Freitag, 22. August 2008, Jan-Oliver Wagner wrote:
> > IMHO, there is no reason why OpenVAS NVT feed shouldn't be changed/extended
> > in its contents/mission in order to suffice the needs of the OSSIM users.
> > Basically this would mean to simply add any available .nasl script that is
> > committed
> > to openvas-plugins (all the SecPod scripts arrived in openvas-plugins trunk
> > already today - thanks to Chandra).
> > The mission of the OpenVAS NVT Feed would then be changed to something like
> > "Newest NVTs from Developer Team's Repository".
> >
> > There are some smaller issues that would need to be discussed (like
> > clever structuring of families, OIDs and so on).
> > In fact I do not see any major blocker why we shouldn't start this right
> > away.
> > Quite the opposite - (even slightly) diverging feed contents, would cause
> > a lot of headache over time when trying to understand/discuss with other
> > some
> > scanning results.
> >
> > Opinions welcome.
>
> if no concerns are expressed, I will do this change as proposed.
> Of course we'd need to announce this prior to the change on openvas-announce.
here is my draft on this:
OpenVAS NVT Feed Change: Extended to Serve Maximum Available
Dear OpenVAS users,
the OpenVAS team plans to extend the current OpenVAS Feed
quite drastically compared to the current coverage [1].
Anyone who configured a OpenVAS Server to use the OpenVAS
NVT Feed should read this announcement carefully.
Currently, the OpenVAS Feed is limited to 100% supported families.
In fact this is just the Debian Local Security Checks.
Thanks to various contributors, the base of NVTs has grown a lot
and is continously improved. Occasional updates of the module
"openvas-plugins" are not sufficient anymore to be reasonably
up-to-date.
Therefore, the OpenVAS Team will accordingly change the policy
of the OpenVAS NVT Feed on
Wednesday, September 10th 2008
There is no change required on your installation.
After the change of the feed, your next synchronisation
will retrieve a lot of more new NASL and INC files than before.
Also, for each NASL and INC file, a signature file will be transfered.
This means, that now all of the NVTs managed in the OpenVAS
source code repository are accompanied with a signature for
transfer integrity, not just the Debian Local Security Check NVTs.
In case you have configured OpenVAS server to only execute signed
NVTs, with the feed change any NVT which is available in the
OpenVAS source code repository will be executed.
Reminder: The applied signatures only guarantees an unmodified
transfer from the OpenVAS Feed service to your OpenVAS Server
installation. The signature does not express a quality measure of
any kind!
Please send your comments or questions to the OpenVAS discussion
mailing list[2].
Best regards
Jan-Oliver Wagner
[1] http://www.openvas.org/openvas-nvt-feed.html
[2] http://lists.wald.intevation.org/mailman/listinfo/openvas-discuss
--
Dr. Jan-Oliver Wagner Intevation GmbH, Osnabrück
Amtsgericht Osnabrück, HR B 18998 http://www.intevation.de/
Geschäftsführer: Frank Koormann, Bernhard Reiter, Dr. Jan-Oliver Wagner
_______________________________________________
Openvas-discuss mailing list
[email protected]
http://lists.wald.intevation.org/mailman/listinfo/openvas-discuss