New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Make Metasploit 5 Development Branch #9259

Merged
merged 5 commits into from Jan 18, 2018

Conversation

Projects
None yet
6 participants
@busterb
Copy link
Contributor

busterb commented Nov 29, 2017

It has been a long, long time coming, but I would like to convert the master branch in git into the Metasploit 5 development branch, maintaining the '4.x' branch in git as the Metasploit 4 stable branch.

This PR bumps the major version as a signifier that we will be landing things that are not 100% compatible with 4.x. Major items that we plan ship in this branch over the next year are:

  • Removal of the current database-backed module cache - Complete
  • Replacing the builtin ActiveRecord-based database layer with a service-oriented version that allows for easier sharing of data (project 'Goliath')
  • Promoting listeners to first class objects (rather than only as side-effects of exploits)
  • Asynchronous session support
  • Improved direct integration with other offensive security tools
  • Improvements in the model for modules
  • Removal of deprecated features
  • Expanding support for module isolation, external modules (project 'Coldstone')
  • Improvements in usability, and some deviations from how Metasploit works today.

PRs that will be going into the 5.x branch will all have the msf5 tag, all others will be cherry picked into the 4.x branch as well.

Good luck everyone!

@busterb busterb changed the title Make Metasploit 5 Make Metasploit 5 Development Branch Nov 29, 2017

@jmartin-r7

This comment has been minimized.

Copy link
Contributor

jmartin-r7 commented Nov 29, 2017

Nightly merge to 4.x has been disabled to facilitate cherry-pick process, this is clear to merge.

@jmartin-r7

This comment has been minimized.

Copy link
Contributor

jmartin-r7 commented Nov 29, 2017

Do we want to make this 5.0.0-alpha? Or are we going to do rolling version bumps weekly even while unstable?

@sempervictus

This comment has been minimized.

Copy link
Contributor

sempervictus commented Nov 30, 2017

Seems only yesterday we were renaming our .msf3 dirs to .msf4... Its growing up quick, soon off to college... :)

busterb and others added some commits Jan 17, 2018

@busterb busterb force-pushed the busterb:msf5 branch from 70a59b8 to 035cdb1 Jan 17, 2018

@busterb

This comment has been minimized.

Copy link
Contributor

busterb commented Jan 18, 2018

it was about 5 years since we announced Metasploit 4. I changed this to not require renaming the major on the config dir just yet, since we haven't actually done anything that needs it.

@wvu-r7

This comment has been minimized.

Copy link
Contributor

wvu-r7 commented Jan 18, 2018

Looks good to me. 👍

busterb added a commit to busterb/metasploit-framework that referenced this pull request Jan 18, 2018

@busterb busterb merged commit 06459e2 into rapid7:master Jan 18, 2018

1 check passed

continuous-integration/travis-ci/pr The Travis CI build passed
Details

@busterb busterb removed the delayed label Jan 18, 2018

@busterb

This comment has been minimized.

Copy link
Contributor

busterb commented Jan 18, 2018

@jmartin-r7 to answer your question, I'd rather not bump versions until we're ready to release on this branch

@busterb busterb deleted the busterb:msf5 branch Jan 18, 2018

@busterb busterb self-assigned this Jan 18, 2018

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment