Am Dienstag, 2. September 2008 19:07:53 schrieb Vlatko Kosturjak: > > Here is a quick proposal for the time being until OID settled: > > > > <ul> > > <li> 1NNNN: Scripts inherited from Nessus > > <li> 2NNNN: Scripts inherited from Nessus > > <li> 3NNNN: Not assigned yet. > > <li> 4NNNN: Not assigned yet. > > <li> 5NNNN: Contributions by Security Space > > <li> 6NNNN: Contributions by Security Space > > <li> 7NNNN: Not assgined yet. > > <li> 8NNNN: Not assgined yet. > > <li> 9NNNN: Contributions by DN Systems > > <li> 10NNNN: Not assgined yet. > > <li> ... > > <li> 20NNNN: Contributions by Ferdy Riphagen > > <li> ... > > <li> 90NNNN: Contributions by SecPod > > </ul> > > > > Anyone: Please let me know if some slipped out of my attention.
According to openvas-libnasl/doc/nasl_guide.tex, the IDs between 90000 and 99000 are intended for private use: "If you plan to distribute your nasl script, then the nessus.org folks will attribute one for you. If you plan to keep your set of scripts private (booo!), then you can use any ID number between 90000 and 99000." Maybe we should continue this scheme and ask contributors without an assigned block to use these numbers; Kost could assign them an 8XXXX number once they are accepted into -plugins. I myself will need a block for OVAL plugins as well; they all have working OIDs as per CR #13, but until we switch OTP to OID-only, I need to have an legacy ID block for them as well. I'll think of a scheme for the IDs and will let you know how many I need. Regards, Michael -- Michael Wiegand OpenPGP key: D7D049EC Intevation GmbH, Osnabrück http://www.intevation.de/ Amtsgericht Osnabrück, HR B 18998 Geschäftsführer: Frank Koormann, Bernhard Reiter, Dr. Jan-Oliver Wagner _______________________________________________ Openvas-plugins mailing list [email protected] http://lists.wald.intevation.org/mailman/listinfo/openvas-plugins
