So if a Tenable plugin was developed, tested, and accepted for a critical vulnerability before a GPL one, this policy could leave the GPL side with never having a plugin available to check for that vuln. At bare minimum you'd have to sign up for the licensed feed to be able to check for that vuln.
At bare minimum, you'd have to register for the free (7 days delayed) feed, yes. For the record, there are over 3,000 non-GPL plugins in the feed today, and that does not seem to have annoyed anyone so far.
Those plugins are currently able to be brought down and used by anyone. Is it wrong to assume that those 3000+ non GPL plugins will be restricted to only those having a "non GPL" feed after the first of the year?
_______________________________________________ Nessus mailing list [EMAIL PROTECTED] http://mail.nessus.org/mailman/listinfo/nessus
