Home page logo

metasploit logo Metasploit mailing list archives

Re: Update surprise
From: James Lay <jlay () slave-tothe-box net>
Date: Tue, 02 Apr 2013 10:33:21 -0600

On 2013-04-02 10:06, Joshua Smith wrote:
This shouldn't have been too big of a surprise, it's been around for
about 3 months:

As the Open Source Issue Manager, someone who does not work for
Rapid7, I can tell you that this actually makes it easier to update
core libraries and such. At the same time, it can be sidestepped for
those that prefer to do so by git cloning the repo and handling the
dependencies yourself. Unfortunately you can't have your cake and eat
it too in this scenario. As a side effect, I imagine it helps to
further justify the continued support of the Metasploit Framework (not the paid versions) when Rapid7 management can see at least some of the
cases when people upgrade from the community edition to the paid
versions. Given all that MSF has gained from the acquisition, I think
this is a small "price" to pay, esp. since it can be side-stepped w/o


On Apr 2, 2013, at 10:56 AM, James Lay wrote:

On 2013-04-02 09:35, Tod Beardsley wrote:

Was this on Kali? The binary installers require some kind of

Thanks for the insight..it does help. As I only run msfconsole and msfupdate (clearly not running the later near enough ;)) I'll go with the github route...truth be told I've never even seen the gui..perhaps that's not a "normal" case usage.



  By Date           By Thread  

Current thread:
[ Nmap | Sec Tools | Mailing Lists | Site News | About/Contact | Advertising | Privacy ]