Bug#323420: Metasploit 3.2 will have new BSD license
On Thu, Nov 6, 2008 at 1:22 AM, Luciano Bello <[EMAIL PROTECTED]> wrote: > Kristian, anarcat and James, >It looks that you are interested in help with this package. Are you > agree if we wait to 3.2 release to start packaging it? Agreed. We will begin after 3.2 is out. Regards... -- Kristian Erik Hermansen http://kristian-hermansen.blogspot.com -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#323420: Metasploit 3.2 will have new BSD license
El Mié 05 Nov 2008, H D Moore escribió: > He is welcome to pull from SVN, however we plan on making some major > changes which should help packaging prior to the 3.2 release. Kristian, anarcat and James, It looks that you are interested in help with this package. Are you agree if we wait to 3.2 release to start packaging it? luciano signature.asc Description: This is a digitally signed message part.
Bug#323420: Metasploit 3.2 will have new BSD license
He is welcome to pull from SVN, however we plan on making some major changes which should help packaging prior to the 3.2 release. These changes would allow a /etc/msfrc file to be used to indicate the directory paths of each component (bin, data, lib, modules, plugins, etc). Still about a week away from being done. On Wednesday 05 November 2008, Kristian Erik Hermansen wrote: > On Wed, Nov 5, 2008 at 10:05 AM, Luciano Bello <[EMAIL PROTECTED]> wrote: > > El Vie 10 Oct 2008, Kristian Erik Hermansen escribi�: > >> Please be advised that inclusion of Metasploit 3.2 will be much > >> easier given the news that a BSD licensed release of Metasploit 3.2 > >> will be available soon! > >> http://www.metasploit.com/blog/#blog-0 > > > > Sorry for the delay, I'm VACed these days (until mid-november). > > > > IIRC, the problem is with the copyright in the payloads and > > shellcodes. Can you check it? > > I don't believe that is an issue any longer. Could someone from the > metasploit legal/dev team please comment on allowing Luciano to pull > MSF 3.2 sources into Debian given the new BSD license? Please advise. > Thanks! -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#323420: Metasploit 3.2 will have new BSD license
On Wed, Nov 5, 2008 at 10:05 AM, Luciano Bello <[EMAIL PROTECTED]> wrote: > El Vie 10 Oct 2008, Kristian Erik Hermansen escribió: >> Please be advised that inclusion of Metasploit 3.2 will be much easier >> given the news that a BSD licensed release of Metasploit 3.2 will be >> available soon! >> http://www.metasploit.com/blog/#blog-0 > > Sorry for the delay, I'm VACed these days (until mid-november). > > IIRC, the problem is with the copyright in the payloads and shellcodes. Can > you check it? I don't believe that is an issue any longer. Could someone from the metasploit legal/dev team please comment on allowing Luciano to pull MSF 3.2 sources into Debian given the new BSD license? Please advise. Thanks! -- Kristian Erik Hermansen http://kristian-hermansen.blogspot.com -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#323420: Metasploit 3.2 will have new BSD license
El Vie 10 Oct 2008, Kristian Erik Hermansen escribió: > Please be advised that inclusion of Metasploit 3.2 will be much easier > given the news that a BSD licensed release of Metasploit 3.2 will be > available soon! > http://www.metasploit.com/blog/#blog-0 Sorry for the delay, I'm VACed these days (until mid-november). IIRC, the problem is with the copyright in the payloads and shellcodes. Can you check it? luciano signature.asc Description: This is a digitally signed message part.
Bug#323420: Metasploit 3.2 will have new BSD license
Please be advised that inclusion of Metasploit 3.2 will be much easier given the news that a BSD licensed release of Metasploit 3.2 will be available soon! http://www.metasploit.com/blog/#blog-0 -- Kristian Erik Hermansen http://kristian-hermansen.blogspot.com -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
