Metasploit Framework
 
 
 
 
 
 
Go to file
James Lee 1ec6884bfa Use before(:each) instead of :all
Fixes deprecation warnings in newer rspec like these

  WARNING: subject accessed in a `before(:all)` hook at:
    /metasploit-framework/spec/lib/rex/post/meterpreter/packet_spec.rb:455:in `block (3 levels) in <top (required)>'

  This is deprecated behavior that will not be supported in RSpec 3.

Also switches to using named subjects for easier reading.
2013-04-25 10:28:30 -05:00
config Add some friendlier defaults to database.yml 2013-04-19 15:43:25 -05:00
data Land #1748, fix for java meterp network prefixes 2013-04-24 12:27:28 -05:00
db Allow use of rake db tasks 2013-03-14 15:46:18 -05:00
documentation Update Gemfile to metasploit_data_models 0.6.1 2013-03-07 14:22:35 -06:00
external Land #1748, fix for java meterp network prefixes 2013-04-24 12:27:28 -05:00
lib Improved docs and partial specs for Rex::Text 2013-04-23 17:24:03 -05:00
modules Add OSVDB ref to sap_configservlet_exec_noauth 2013-04-25 08:13:32 -05:00
plugins indentation compliance 2013-03-07 14:57:03 -05:00
scripts Update keylogrecorder.rb 2013-03-22 10:57:10 -07:00
spec Use before(:each) instead of :all 2013-04-25 10:28:30 -05:00
test Have Post::File use shiny new session.fs.file.mv 2013-04-05 01:24:24 -05:00
tools msftidy cleanup 2013-04-12 21:39:11 +02:00
.gitignore Adding new .gitignores 2013-04-08 22:01:46 -05:00
.mailmap Alphabetized .mailmap 2013-04-15 15:40:26 -05:00
.rspec Fix missed rename when adding fastlib under directory 2012-10-08 16:14:37 -05:00
.simplecov Better Rubymine compatibility for .simplecov 2013-01-18 11:12:16 -06:00
.travis.yml Configure travis-ci to use database for rake spec 2013-03-15 08:48:20 -05:00
.yardopts Merge pull request #1563 from rapid7/bug/yard-guard 2013-03-07 17:35:03 -06:00
CONTRIBUTING.md Update CONTRIBUTING.md 2012-12-21 09:48:13 -06:00
COPYING Replace THIRD_PARTY with machine-readable LICENSE 2013-01-08 13:38:18 -06:00
Gemfile Move optional gems to bundler groups 2013-04-12 09:47:40 -05:00
Gemfile.lock Use metasploit_data_models from rubygems 2013-04-11 15:35:19 -05:00
HACKING Adding bundler step to HACKING 2013-04-05 10:18:58 -05:00
LICENSE Fix typo 2013-04-23 15:39:02 -05:00
README.md Merge branch 'feature/contributing' of https://github.com/todb-r7/metasploit-framework into todb-r7-feature/contributing 2012-11-13 21:44:42 +01:00
Rakefile Fix specs with bundler groups 2013-04-12 10:46:00 -05:00
msfbinscan
msfcli Fix module reloading 2012-10-04 16:32:12 -05:00
msfconsole Fully deprecates msfupdate over SVN 2013-03-14 15:21:33 -05:00
msfd
msfelfscan
msfencode
msfmachscan
msfpayload
msfpescan
msfrop
msfrpc Remove unused option. 2013-03-25 20:47:18 -05:00
msfrpcd
msfupdate Automatically update gems after running msfupdate 2013-04-05 09:42:15 -05:00
msfvenom Import datastore options when using an encoder 2013-01-10 17:11:58 -06:00

README.md

Metasploit Build Status Code Climate

The Metasploit Framework is released under a BSD-style license. See COPYING for more details.

The latest version of this software is available from http://metasploit.com/

Bug tracking and development information can be found at: https://dev.metasploit.com/redmine/projects/framework/

The public GitHub source repository can be found at: https://github.com/rapid7/metasploit-framework

Questions and suggestions can be sent to: msfdev(at)metasploit.com

The framework mailing list is the place to discuss features and ask for help. To subscribe, visit the following web page: https://mail.metasploit.com/mailman/listinfo/framework

The mailing list archives are available from: https://mail.metasploit.com/pipermail/framework/

Installing

Generally, you should use the installer which contains all dependencies and will get you up and running with a few clicks. See the Dev Environment Setup if you'd like to deal with dependencies on your own.

Using Metasploit

Metasploit can do all sorts of things. The first thing you'll want to do is start msfconsole, but after that, you'll probably be best served by reading some of the great tutorials online:

Contributing

See the Dev Environment Setup guide on GitHub which will walk you through the whole process starting from installing all the dependencies, to cloning the repository, and finally to submitting a pull request. For slightly more info, see Contributing.