Make Metasploit 5 Development Branch

[busterb]

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!

[jmartin-tech]

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

[jmartin-tech]

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

[sempervictus]

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

[busterb]

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]

Looks good to me. 👍

[busterb]

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