Metasploit框架安装

Metasploit Development Environment

This is a guide for setting up an environment for effectively contributing to the Metasploit Framework. If you just want to use Metasploit for legal, authorized hacking, we recommend instead you download the Metasploit binary installer, which will take care of all the dependencies and give you access to the open source Metasploit Framework, the free Metasploit Community edition, and an option to start the free trial for Metasploit Pro.

If you're using Kali Linux, Metasploit is already pre-installed for non-development purposes; just type msfconsole in the terminal to start Metasploit Framework, then type go_pro if you'd like to try Metasploit Pro or Metasploit Community.

If you actually want to develop on and contribute to Metasploit, read on!

Getting Started

We assume that you're on some recent version of Ubuntu Linux. If not, then you're going to be on your own on how to get all your dependencies lined up . If you've successfully set up a development environment on something non-Ubuntu, and you'd like to share, let us know and we'll link to your tutorial from here.

Please note that Kali Linux (formerly Backtrack Linux) is not very suitable as a development environment, and you may run into missing upstream packages. It's a great place to use Metasploit, but not so great for hacking on it directly.

Throughout this documentation, we'll be using the example user of "Fakey McFakepants," who has the e-mail address of "mcfakepants@packetfu.com" and a login username of "fakey."

Note that this does not include an appropriate text editor or IDE, nor does it include the Ruby interpreter. We'll get to that in a second.

Getting Ruby

Many standard distributions of Ruby are lacking in one regard or another. Lucky for all of us, Wayne Seguin's RVM has become quite excellent at providing several proven Ruby interpreters. Visithttps://rvm.io/ to read up on it or just trust that it'll all work out with a simple:

Next, load the RVM scripts by either opening a new terminal window, or just run:

source ~/.rvm/scripts/rvm

If you must be root (eg, on BackTrack or Kali), then you will need to explicitly add this (slightly different) line to the end of /root/.bashrc, instead:

source /usr/local/rvm/scripts/rvm

Finally, you will usually need to tick the Run command as login shell on the default profile of gnome-terminal (assuming stock Ubuntu), or else you will get the error message that RVM is not a function.

Assuming all goes as planned, you should end up with something like this in your shell:

Because Metasploit now ships with .ruby-gemset and .ruby-version files, you do not need to do anything special to ensure your gems get stashed in the right place. When you cd to your Metasploit framework checkout, your environment will automatically switch contexts to ruby-1.9.3@metasploit-framework.

Your Editor

Once that's done, you can set up your preferred editor. Far be it from us to tell you what editor you use -- people get really attached to these things for some reason. An informal straw poll shows that many Metasloit developers use vim, some use Rubymine, and a few use emacs or Sublime Text 2 (or 3), for which here is some helpful awesomesauce similar to what's below. For this document, let's say you're a vim kind of person, since it's free.

First, get vim, your usual way. Vim-gnome is a pretty safe bet.

sudo apt-get install vim-gnome -y

Next, get Janus. Janus is a set of super-useful plugins and conveniences for Vim. You can read up on it here: https://github.com/carlhuda/janus . Or, again, just trust that Things Will Be Fine, and:

curl -Lo- https://bit.ly/janus-bootstrap | bash

This will checkout a version of Janus (using Git) to your ~/.vim directory. Yep, you now have a git repo in one of your more important dot-directories.

Finally, I have a very small set of defaults, here: https://gist.github.com/4658778 . Drop this in your~/.vimrc.after file. Note, Metasploit no longer uses hard tabs.

Using GitHub

The entire Metasploit code base is hosted here on GitHub. If you have an old Redmine account over at https://dev.metasploit.com, that's not going to provide authentication and identification on GitHub (but we still take bugs over on Redmine).

Alias GitHub in .ssh/config

I hate having to remember usernames for anything anymore, so I've gotten in the habit of creating Host entries for lots of things in my ~/.ssh/config file. You should try it, it's fun, and it can shorten most of your ssh logins to two words.

For the rest of these instructions, I'm going to assume you have something like this in your config file:

To check that it works, just ssh -T github, and your result should look like this:

Git aliases

Git is super and everything, but sometimes the commands can be too arcane, verbose, or long. For that, @todb-r7 has shared a pile of git aliases that he uses, strategically stashed in his online junk drawer. These are useful for both regular contributors and members of the Metasploit Committers Team, so unless you like a lot of memorization and sore fingers, you might want to pick and chose from there what makes sense for you and your workflow.

Working with Git

The rest of this document will walk through the usual use case of working with Git and GitHub to get a local source checkout, commit something new, and get it submitted to be part of the Metasploit Framework distribution.

The example here will commit the file 2.txt to test/git/ , but imagine that we're committing some new module like ms_12_020_code_exec.rb to modules/exploits/windows/rdp/.

Forking Metasploit

Hang out for a few seconds, and behold the animated "Hardcore Forking Action":

After that's done, switch back over to your terminal, make a sub-directory for your git clones, and use your previously defined .ssh/config alias to clone up a copy of Metasploit. Note that usernames on GitHub are case-sensitive; McFakePants is different from mcfakepants.

You should end up with a complete copy of Metasploit in the metasploit-framework sub-directory:

Setting Your Prompt

Now might be a good time to decorate your prompt. At the minimum, you will want something like this in your ~/.bash_aliases to let you know on the prompt which branch you're in, if you're in a git repo. I have no idea how else you would be able to track what branch you're in, honestly.

In the end, you'll have a prompt that looks like:

(master) fakey@mazikeen:~/git/metasploit-framework$

where the master bit changes depending on what branch you're in.

Bundle Install

The first time you download Metasploit, you will need to get your Ruby gems lined up. It's as simple as gem install bundle && bundle install from your metasploit-framework checkout. It'll look like this:

From that point on, you'll want to occasionally run bundle install whenever the Gemfilechanges (msfupdate does this automatically).

You do not want to run bundle update by itself, ever, unless you are very serious about updating every Gem in your gemset to some unknown bleeding-edge version.

Configure Your Database

While it's possible to run Metasploit without a database, it's growing increasingly uncommon to do so. The fine folks over at the Fedora Project Wiki have a snappy guide to get your database configured for the first time, here: https://fedoraproject.org/wiki/Metasploit_Postgres_Setup

Once that's complete, rename your database.yml.example file to 'database.yml' and be sure to fill in at least the "development" and "test" sections.

Start Metasploit

Now that you have a source checkout of Metasploit and you have all your prerequisite components from apt, rvm, and bundler, you should be able to run it straight from your git clone with./msfconsole -L:

Note that if you need resources that only root has access to, you'll want to run rvmsudo ./msfconsole -L instead.

To start off connected to a database, you will want to run something like ./msfconsole -L -y config/database.yml -e development

Keeping In Sync

One of the main reasons to use Git and GitHub is this whole idea of branching in order to keep all the code changes straight. In other source control management systems, branching quickly becomes a nightmare, but in Git, branching happens all the time.

You start off with your first branch, "master," which you pretty much never work in. That branch's job is to keep in sync with everyone else. In the case of Metasploit, "everyone else" israpid7/metasploit-framework/branches/master. Let's see how you can keep up with the upstream changes via regular rebasing from upstream's master branch to your master branch.

Check out the upstream master branch

This is pretty straightforward. From your local branch on the command line, you can:

This lets you peek in on upstream, after giving a warning about being in the "detatched HEAD" state (don't worry about that now). From here you can do things like read the change log:

git log --pretty=oneline --name-only -3

It should all look like this in your command window:

It's pretty handy to have this checkout be persistent so you can reference it later. So, type this:

git checkout -b upstream-master

And this will create a new local branch called "upstream-master." Now, switch back to your master branch and fetch anything new from there:

git checkout master
git fetch

And finally, rebase against your local checkout of the upstream master branch:

git rebase upstream-master

Rebasing is the easiest way to make sure that your master branch is identical to the upstream master branch. If you have any local changes, those are "rewound," all the remote changes get laid down, and then your changes get reapplied. It should all look like this:

Of course, you might occasionally run into rebase conflicts, but let's just assume you won't for now. :) Resolving merge conflicts is a little beyond the scope of this document, but the Git Community Book should be able to help. In the meantime, we're working up another wiki page to deal specifically with the details of merging, rebasing, and conflict resolution.

Note that you can skip the checkout to a local branch and simply always git rebase upstream/master as well, but you then lose the chance to review the changes in a local branch first -- this can make unwinding merge problems a little harder.

A note on terminology: In Git, we often refer to "origin" and "master," which can be confusing. "Origin" is a remote repository which contains all of your branches. "Master" is a branch of the source code -- usually the first branch, and the branch you don't tend to commit directly to.

"Origin" isn't Rapid7's repository -- we usually refer to that repo as "Upstream." In other words, "upstream" is just another way of referring to the "rapid7" remote.

Got it? "Origin" is your repo up at GitHub, "upstream" is Rapid7's GitHub repo, and "master" is the primary branch of their respective repos.

All right, moving on.

Syncing changes

Any time you rebase from upstream (like just now), you're likely to bring in new changes because we're committing stuff all the time. This means that when you rebase, your local branch will be ahead of your remote branch. To get your remote fork up to speed:

git push origin master

It should all look something like this:

Switch back to your browser, refresh, and you should see the new changes reflected in your repo immediately (those GitHub guys are super fast):

Pull Requests

Finally, let's get to pull requests. That's why you're reading all this, after all. Thanks to@corelanc0d3r for initially writing this all down from a contributor's perspective.

First, create a new branch from your master branch:

git checkout master
git checkout -b module-ms12-020

Write the module, putting it in the proper sub-directory. Once it's all done and tested, add the module to your repo and push it up to origin:

In your browser, go to your newly created branch, and click Pull Request.

This will automatically reference upstream's master as the branch to land your pull request, and give you an opportunity to talk about how great your module is, what it does, how to test it, etc.

Once you click Send Pull Request, you'll be on upstream's pull queue (in this case, mcfakepants has created pull request #356, which is one of 17 open pull requests).

Depending on the position of the stars, someone from the Metasploit core development team will review your pull request, and land it, like so:

Now, keep in mind that actually landing pull requests is a little more involved than just taking your commit and applying it directly to the tree. Usually, there are a few changes to be made, sometimes there's some back and forth on the pull request to see if some technique works better, etc. To have the best chance of actually getting your work merged, you would be wise to consult the [[guidelines for accepting modules and enhancements]].

The upshot is, what's committed to Metasploit is rarely exactly what you initially sent, so once the change is committed, you'll want to rebase your checkout against master to pick up all the changes. If you've been developing in a branch (as you should), you shouldn't hit any conflicts with that.

Cleaning up

Now that everything's committed and you're rebased, if you'd like to clean out your development branches, you can just do the following:

git branch -D module-ms12-020
git push origin :module-ms12-020

Note that Git branches are cheap (nearly free, in terms of disk space), so this shouldn't happen too terribly often.

Git Hooks

If you plan to work on Metasploit, you should have the standard pre-commit and post-merge symlinks set up. This is really easy; assuming you're in the top-level directory of a Metasploit framework checkout, just type:

This will run this now somewhat misleadingly-named pre-commit-hook.rb before every commit you make, and after every merge, to check your modules. The pre-commit hook will prevent you from checking in modules that don't pass msftidy.rb inspection, while post-merge will merely ask you nicely to not merge new brokenness.

To skip the pre-commit test because nobody's the boss of you, just run your git commitcommand with the --no-verify option. Note that actually submitting broken modules will make them unlikely landing candidates by the Metasploit Committer Team since they all run the same checks before landing.

RSpec Tests

We are slowly lurching toward a normal testing environment, now require rspec tests to validate changes to the core workings of the framework. To get in the habit, run the standard set of tests against your local Metasploit branch. First, make sure you have all the gems installed, then run therake spec task.

gem install bundler # Only need to do this once
$ bundle install
rake spec # Do this in the top-level Metasploit root

For more on rspec (which is the de-facto testing standard for Ruby projects), see http://rspec.info/and http://betterspecs.org. To add tests, drop them someplace sensible in the spec directory, and name your tests whatever_spec.rb.

Signed commits

While not required for most committers, the Metasploit Committer Team does sign all of their commits, using this procedure. Trust me, it's delightfully fun, especially since barely anyone actually signs commits out in GitHub land. If you would like to validate signatures (and you should!), you'll want to snag that list of Committer Keys, as well.

Next Steps

First off, thanks to @corelanc0d3r for articulating much of this. If you have suggestions for this wiki, please let @todb-r7 know.

This document should be enough to get your Metasploit development career started, but it doesn't address huge areas of Git source control management. For that, you'll want to look at the Git Community Book, the many answered questions on StackOverflow, and the git cheat sheet.

Finally, you will want to initialize your mind grapes with the CONTRIBUTING.md document which we all slavishly follow and has more code style and content details that you should be aware of.

Also, we're serious about that word "career" -- if you'd like to work on Metasploit full time, just droptodb@metasploit.com a line with your resume and see if there are any current or upcoming openings.