Matthew Mundell wrote: >> It would be good to have timestamps for NVTs >> that describe first release and perhaps latest change. >> Maybe also the revision in a processable way >> to have this available in the manager database. >> OpenVAS Manager could the inform about latest >> 5 new NVTs or latest 5 Updated NVTs. >> >> The easiest way is to use tags. >> Are there better options? >> How to manage the old stuff? Leave as is? >> >> Brain storming welcome ;-) > > The version could be built into the OID. Like as a suffix. Each version > of the NVT would have a unique OID.
Ugh... (-) vote here. If the OIDs are not consistent across different versions of the script, taking baseline audits becomes a problem, because now all the IDs might change from one audit to the next, despite nothing actually changing on the network. I wouldn't recommend overloading the script OID in that way. Tags are probably the way to go. For older scripts, just set the date to something old, with nothing "older", such as "20050101", which can be place holder for anything older than that. Thomas _______________________________________________ Openvas-devel mailing list Openvas-devel@wald.intevation.org http://lists.wald.intevation.org/mailman/listinfo/openvas-devel
