In my opinion, the new licensing should not prevent you from putting a plugin into the Tenable feed:
- we will maintain it - we will enhance it - we will keep your name on it - we will answer the support tickets and mailing lists questions Usually, organizations that have some sort of issue contributing back plugins result from some sort of intellectual property policy preventing them to do so in the first place. This was one of the big changes we made to the feeds years ago, simply because most Nessus users were users and not developers or plugin writers. I've also had some organizations claim they don't want to write plugins because they don't want to be liable for a DOS event (not that Tenable would likely let such a destructive plugin out). If you do want to distribute your own plugins, you are certainly free to do so. If you don't want us to distribute the plugins because you are afraid we might make money off of them, what do you think most of the MSPs, consultants, and audits who will use your plugin will do then? Ron Gula Tenable Network Security Doug Nordwall wrote: > The new licensing presents an interesting problem for those of us who > occasionally contribute/write modules. We may write something for work, and > we're happy with it. We may even want to share it from the community. It may > get legally sticky when another company (Tenable) is making money off of it > because another company (Company A) cannot get the plugin for free, because > they can't use the home version for a commercial license, and there isn't a > registered feed version. I know for my own company, this would get the > lawyers all up in arms because if Tenable is selling it, why can't we sell > it? If someone can sell it, why do I, the developer, want to give it away? > Ya, I know it's kind of asinine, I swear I've seen very similar sorts of > situations. > > I've not read the new license in a lot of detail, but is there anything that > prevents a plugin writer from distributing it freely on his own _and_ keeps > it from being distributed by Tenable? Not that I want to gouge Tenable's > business (we have several feeds and love them), but there is a potential > issue for some folks. > _______________________________________________ Nessus mailing list [email protected] http://mail.nessus.org/mailman/listinfo/nessus
