-
Notifications
You must be signed in to change notification settings - Fork 14.1k
Merging Metasploit Payload Gem Updates
OJ Reeves edited this page Dec 7, 2016
·
6 revisions
When the Metasploit Payloads has a new merge appear in master
, a new Ruby gem is built and automatically pushed up to RubyGems. This new version needs to be merged into the Metasploit Framework repository for those changes to be included.
To do this, committers must:
- Create a new branch in the Metasploit Framework repository.
- Name it something useful like
metasploit-payloads-<version>
. - Modify
metasploit.gemspec
, so that the new version number is specified for themetasploit-payloads
gem. - Run
bundle install
. - Remove any test/development binaries from
data/meterpreter
. - Run
tools/modules/update_payload-cached_sizes.rb
. - Make sure that
Gemfile.lock
only contains changes that are related to Metasploit Payloads. - Stage the following for commit in
git
:Gemfile.lock
metasploit.gemspec
- Any payload modules that have had an updated payload size (usually this includes stageless payloads only)
- Commit the staged files.
- Push the branch to github.
- Create the Pull Request.
Done!
- Home Welcome to Metasploit!
- Using Metasploit A collection of useful links for penetration testers.
-
Setting Up a Metasploit Development Environment From
apt-get install
togit push
. - CONTRIBUTING.md What should your contributions look like?
- Landing Pull Requests Working with other people's contributions.
- Using Git All about Git and GitHub.
- Contributing to Metasploit Be a part of our open source community.
- Meterpreter All about the Meterpreter payload.