Hi Bret,
what about the file sigvi-2.0.0.sql in the sigvi-2.0.0 directory of the tarball?
It's 54MB big once uncompressed... maybe you lost it somehow?
The huge part of the dump is the vulnerability dump. I'm still unsure if I want to import everything. I would better not import this table, and manually through the GUI let SIGVI fetch the 2010 and maybe 2009 vulnerability DB. (older vuln have some strange CPE naming, NIST has changed their way of naming along the way)
There's one issue though: the parsing is a little bit dodgy, and crashes upon memory and time exhaustion... still, if you repeat the loading, you will finally end up with a complete DB.
Hope it helps.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hi Bret,
what about the file sigvi-2.0.0.sql in the sigvi-2.0.0 directory of the tarball?
It's 54MB big once uncompressed... maybe you lost it somehow?
The huge part of the dump is the vulnerability dump. I'm still unsure if I want to import everything. I would better not import this table, and manually through the GUI let SIGVI fetch the 2010 and maybe 2009 vulnerability DB. (older vuln have some strange CPE naming, NIST has changed their way of naming along the way)
There's one issue though: the parsing is a little bit dodgy, and crashes upon memory and time exhaustion... still, if you repeat the loading, you will finally end up with a complete DB.
Hope it helps.