Community Packages

Please read this before reporting a bug:
http://wiki.archlinux.org/index.php/Reporting_Bug_Guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#67266 - [metasploit] v6 Packaging

Attached to Project: Community Packages
Opened by Spencer McIntyre (zeroSteiner) - Monday, 13 July 2020, 19:17 GMT
Last edited by freswa (frederik) - Monday, 13 July 2020, 21:21 GMT
Task Type Support Request
Category Packages
Status Assigned
Assigned To Levente Polyak (anthraxx)
Architecture All
Severity Medium
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 0%
Votes 0
Private No

Details

Hi, this is Spencer McIntyre from the Metasploit Framework team, and I wanted to let you know about some important upcoming changes. On July 23rd we are planning on merging the latest code for our upcoming 6th version into our master branch on GitHub. This is going to mark us publishing quite a few new features and changes, some of which are not backwards compatible. Until such time that we have determined the 6th version to be stable, we are asking project maintainers to continue packaging the stable 5.x version. This will be available on GitHub within the [5.x](https://github.com/rapid7/metasploit-framework/tree/5.x) branch.

One of the most important things for users to note is that Meterpreter sessions generated from version 5 will not be able to connect to version 6 of the framework and vice versa. For this reason it’s important that users do not upgrade Metasploit from 5 to 6 while they are actively using it on operations.

Once we’re ready to call version 6 stable and have it shipped I will update you again to let you know. We want to work closely with our community package maintainers and provide you with enough warning to take any actions necessary. There will be a more formal announcement posted to the [Metasploit Blog](https://blog.rapid7.com/tag/metasploit/) on release day that will outline the changes in more detail. If you have any questions in the meantime, please don’t hesitate to ask.
This task depends upon

Comment by Spencer McIntyre (zeroSteiner) - Monday, 13 July 2020, 21:11 GMT
There actually will not be a maintained 5.x branch. Instead, the last stable 5.x version will be identified by the last 5.0.x Git [tag](https://github.com/rapid7/metasploit-framework/tags).
Comment by Spencer McIntyre (zeroSteiner) - Friday, 31 July 2020, 18:17 GMT
Just a quick update on this, we've had to postpone the release and are now targeting Thursday August 6th for merging the v6 changes into master. Thanks!
Comment by Spencer McIntyre (zeroSteiner) - Thursday, 06 August 2020, 18:04 GMT
So today is August 6th, and as planned Metasploit has merged in the changes as part of the v6 development. The official announcement is available here https://blog.rapid7.com/2020/08/06/metasploit-6-now-under-active-development/. So at this time we're asking that you please continue to ship version 5 for the time being until we determine that 6 is stable.
Comment by Levente Polyak (anthraxx) - Sunday, 30 August 2020, 10:33 GMT
Just a small feedback because it was quite silent here: Thanks a lot for reaching out to us directly, this is very much appreciated. I will test v6 soon and hopefully give feedback if there are some packaging issues.
Comment by Levente Polyak (anthraxx) - Friday, 16 October 2020, 21:18 GMT
zeroSteiner, what the current status with metasploit?
Comment by Spencer McIntyre (zeroSteiner) - Monday, 19 October 2020, 14:52 GMT
Since version 6.0.10 we've fixed the last issue we're aware of at this time that are related to the version 6 changes. It's now ready for projects to resume packaging the main branch. Thanks for working with us on this!

Loading...