Seems to me that the maximum size is virtually unlimited. If you have x machines and scan for y vulnerabilities then the maximum size is going to be along the lines of x * (y + z) * k where z represents the overhead of the scan (housekeeping plugins and results) and k is the average size of an nbe record. Even if you have x frozen at a certain size the value of y is likely to vary over time.
I import the result data (nbe) into Oracle via a home-grown script and the only size problem I have encountered to date was a reluctance on the part of the dba's to size the fields as indicated. Consequently I have to truncate the message in some cases (they fixed it at 4,000 chars if I remember correctly). Tim Doty -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of jamjam Sent: Thursday, October 04, 2007 5:51 AM To: [email protected] Subject: nbe file size Hello, Generally when we scan an entire class C our resulting nbe file is usually about 1.5 MB. Although we have seen larger nbe files, I've never seen one over 3 MB. We will soon be importing our nbes into either a MySQL or Postgresql database and I understand that there are limits in both apps as to the size of the imported data. So, I guess my question is, is how large can a nbe file get? Thanks!
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________ Nessus mailing list [email protected] http://mail.nessus.org/mailman/listinfo/nessus
