On Dienstag, 30. Juni 2015, Public Account wrote: > Then, as Timo suggested: > rm /usr/local/var/lib/openvas/scap-data/scap.db > /usr/local/sbin/openvas-scapdata-sync > > Again same version (201506240629) but this time the CVE is there !! Bingo! > > So, some questions arise: > - Any clue why this could happen?
not really ;-) > - Any clue about how to detect there's a problem in the db (before > discovering you are missing a CVE)? I am unsure whether it was a detectable problem. Maybe the db was correct as such, just using some wrong assumption about timestamps. > - It's a good policy to, once a month for example, delete scap.db and > resync? Not in my opinion. One the one hand I've not seen similar problems and on the other hand we won't find out easily about a problem with such a workaround. -- 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 _______________________________________________ Openvas-discuss mailing list [email protected] https://lists.wald.intevation.org/cgi-bin/mailman/listinfo/openvas-discuss
