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.
On Fri, May 16, 2008 at 10:55 AM, Ron Gula <[EMAIL PROTECTED]>
wrote:
> Hi Chris,
>
> I'm sorry that you don't want to share your plugins with the rest of the
> Nessus community. We really encourage you to do so.
>
> If you do write a Nessus plugin and want to give it to someone else,
> you are free to do that. If they already have Nessus and the .inc files
> you are calling, then there is no issue.
>
> Also, there is a plugin-writers mailing list. Sometimes folks who write
> NASL plugins don't necessarily share thier code, but their ideas which
> I'd also encourage you to do.
>
> Ron Gula
> Tenable Network Security
>
>
> Chris Covington wrote:
> > Since the Nessus program use itself has been made more restricted, it
> there a chance that the license terms for the Nessus plugins could be
> relaxed slightly?
> >
> > I.e. I would like to write a few custom plugins that rely on functions in
> existing Tenable .inc files, specifically the ones necessary to talk to
> Microsoft systems. These custom plugins would not copy code, they would
> just call functions contained in Tenable .inc files (e.g.
> include("smb_func.inc")). I would like to share those custom plugins
> (without needing to share Tenable .inc files) with a couple of other similar
> organizations but not have to first send Tenable a copy of the plugin and
> ask for Tenable's permission to share custom plugin code that my
> organization will have spent its own time and effort to create, especially
> since my organization pays Tenable a yearly subscription fee.
> >
> > Thank you for considering,
> >
> > Chris Covington
> _______________________________________________
> Nessus mailing list
> [email protected]
> http://mail.nessus.org/mailman/listinfo/nessus
>
--
Doug Nordwall
Unix, Network, and Security Administrator
You mean the vision is subject to low subscription rates?!!? - Scott Stone,
on MMORPGs
_______________________________________________
Nessus mailing list
[email protected]
http://mail.nessus.org/mailman/listinfo/nessus
