Ahem, http://mail.metasploit.com/pipermail/framework/2010-September/006889.html
A bit of msf licensing history is mentioned here (and abuses): http://blog.metasploit.com/2008/10/metasploit-32-bsd-licensing.html "The new license will lead to commercial abuse, but I believe that the project is now strong enough to succeed even with competition from commercial entities that are using our source code. The key to our success is the Metasploit community and our dedication to sharing security information (and code) in a timely fashion. Metasploit is great at destroying FUD, whether the source is an incompetent product vendor or a media-happy security company. " -Patrick On Thu, Sep 1, 2011 at 3:51 AM, <valdis.kletni...@vt.edu> wrote: > On Wed, 31 Aug 2011 14:34:58 -0300, root said: > >> That file is under the msf3 tree, if Insect pro is violating GPL, >> Metasploit is also doing it (and everything including it, like 80% of >> security frameworks out there), remember MSF is BSD licensed. > > And even the top-level Metasploit HACKING says: > > By submitting code contributions to the Metasploit Project it is > assumed that you are offering your code under a BSD or similar > license. MIT and Ruby Licenses are also fine. We specifically cannot > include GPL code. LGPL code is accepted on a case by case basis for > libraries only and is never accepted for modules. _______________________________________________ Full-Disclosure - We believe in it. Charter: http://lists.grok.org.uk/full-disclosure-charter.html Hosted and sponsored by Secunia - http://secunia.com/
