github
/
metasploit-framework
mirror of https://github.com/rapid7/metasploit-framework
1
Fork 0
Code Releases Activity
metasploit-framework/.gitignore

Ignoring revisions in .git-blame-ignore-revs. Click here to bypass and see the normal blame view.

105 lines
2.6 KiB
Plaintext
Raw Permalink Normal View History

Replacing with master's .gitignore
2013-04-09 04:52:35 +02:00
.bundle
Added support for Gemfile.local
2014-02-21 20:37:31 +01:00
Gemfile.local
Gemfile.local.lock
Give ruby Modules that wrap Metasploit modules a name [#36737359] active_support/dependencies cannot resolve missing constants in Metasploit modules because the wrapper module is anonymous. In order to make the wrapper module non-anonymous, the module must be assigned to a constant. Since we don't want modules colliding, the wrapper module needs a unique name, so use the module lookup name to derive the proper nested module names to namespace the wrapper module. All derived modules are nested under Msf::Modules. The name derivation handles invalid characters for constant names such as digits as the first character or non-alphanumeric character. The invalid constant name characters are converted to their hex value and prefixed with X, so '-' in a name become 'X2d'.
2012-09-27 19:52:09 +02:00
# Rubymine project directory
.idea
Add in Visual Studio Code .vscode directory to .gitignore
2022-09-01 02:44:49 +02:00
# Visual Studio Code configuration settings directory
.vscode
add .sublime-project to gitignore
2013-08-16 05:25:29 +02:00
# Sublime Text project directory (not created by ST by default)
.sublime-project
Remove gitignore, change to metasploit-framework
2013-09-13 19:44:19 +02:00
# RVM control file, keep this to avoid backdooring Metasploit
Remove .rvmrc Remove .rvmrc from source control and add it to .gitignore so it can't be readded.
2012-10-02 23:29:22 +02:00
.rvmrc
Allow for locally chosen rubies By ignoring .versions.conf, we can allow users pick their own versions of ruby without having to jump through a bunch of hoops on keeping .ruby-version straight between local and remote branches.
2014-11-05 20:15:32 +01:00
# Allow for a local choice of (unsupported / semi-supported) ruby versions
Add note about rbenv for rvm .versions.conf local override
2014-11-06 00:03:02 +01:00
# See PR #4136 for usage, but example usage for rvm:
typo
2014-11-05 20:19:40 +01:00
# rvm --create --versions-conf use 2.1.4@metasploit-framework
Add note about rbenv for rvm .versions.conf local override
2014-11-06 00:03:02 +01:00
# Because rbenv doesn't use .versions.conf, to achieve this same functionality, run:
# rbenv shell 2.1.4
Allow for locally chosen rubies By ignoring .versions.conf, we can allow users pick their own versions of ruby without having to jump through a bunch of hoops on keeping .ruby-version straight between local and remote branches.
2014-11-05 20:15:32 +01:00
.versions.conf
Remove .rvmrc Remove .rvmrc from source control and add it to .gitignore so it can't be readded.
2012-10-02 23:29:22 +02:00
# YARD cache directory
Refactor Msf::ModuleManager [Fixes #36737359] Refactor Msf::ModuleManager into concerns so its easier to understand and duplicate code can be made DRY. The refactoring also ensures that when loading from directories, Fastlibs, or reloading, the wrapper module will always be named so that activesupport/dependencies will function.
2012-10-01 20:09:30 +02:00
.yardoc
Give ruby Modules that wrap Metasploit modules a name [#36737359] active_support/dependencies cannot resolve missing constants in Metasploit modules because the wrapper module is anonymous. In order to make the wrapper module non-anonymous, the module must be assigned to a constant. Since we don't want modules colliding, the wrapper module needs a unique name, so use the module lookup name to derive the proper nested module names to namespace the wrapper module. All derived modules are nested under Msf::Modules. The name derivation handles invalid characters for constant names such as digits as the first character or non-alphanumeric character. The invalid constant name characters are converted to their hex value and prefixed with X, so '-' in a name become 'X2d'.
2012-09-27 19:52:09 +02:00
# Mac OS X files
.DS_Store
Ignore .solargraph.yml config file
2023-05-17 22:03:05 +02:00
# Ignore Solargraph config file
.solargraph.yml
Replacing with master's .gitignore
2013-04-09 04:52:35 +02:00
# database config for testing
config/database.yml
renaming targets.yml to .example ignoring the targets.yml file
2014-08-14 00:40:51 +02:00
# target config file for testing
features/support/targets.yml
Add tests for aux and exploit cmd_check and cmd_run
2021-06-25 12:46:44 +02:00
# Generated test files
spec/dummy
Add simplecov for code coverage Conflicts: Gemfile.lock
2012-11-06 23:30:41 +01:00
# simplecov coverage data
coverage
Replacing with master's .gitignore
2013-04-09 04:52:35 +02:00
doc/
external/source/meterpreter/java/bin
external/source/meterpreter/java/build
external/source/meterpreter/java/extensions
external/source/javapayload/bin
external/source/javapayload/build
Adding new .gitignores
2013-04-09 05:01:46 +02:00
# Java binary ignores. Replace the 5 above with this once we're merged.
external/source/javapayload/*/.classpath
external/source/javapayload/*/.project
external/source/javapayload/*/.settings
external/source/javapayload/*/bin
external/source/javapayload/*/target
external/source/javapayload/*/*/.classpath
external/source/javapayload/*/*/.project
external/source/javapayload/*/*/.settings
external/source/javapayload/*/*/bin
external/source/javapayload/*/*/target
Give ruby Modules that wrap Metasploit modules a name [#36737359] active_support/dependencies cannot resolve missing constants in Metasploit modules because the wrapper module is anonymous. In order to make the wrapper module non-anonymous, the module must be assigned to a constant. Since we don't want modules colliding, the wrapper module needs a unique name, so use the module lookup name to derive the proper nested module names to namespace the wrapper module. All derived modules are nested under Msf::Modules. The name derivation handles invalid characters for constant names such as digits as the first character or non-alphanumeric character. The invalid constant name characters are converted to their hex value and prefixed with X, so '-' in a name become 'X2d'.
2012-09-27 19:52:09 +02:00
# Packaging directory
pkg
Ignore tags and swap files
2011-11-16 18:57:59 +01:00
tags
*.swp
Don't commit leftovers from failed patches
2012-03-16 23:28:16 +01:00
*.orig
*.rej
Replacing with master's .gitignore
2013-04-09 04:52:35 +02:00
*~
Add *.notab to gitignore These are artifacts of tools/dev/retab.rb
2013-08-07 18:39:36 +02:00
# Ignore backups of retabbed files
*.notab
Move kitrap0d exploit from getsystem to local exploit This version modifies the existing meterpreter session and bumps the privs up to SYSTEM. However it's not how local exploits are supposed to work. More work will be done to make this create a new session with the elevated privs instead.
2013-11-11 02:11:42 +01:00
# ignore Visual Studio external source garbage
*.suo
*.sdf
*.opensdf
*.user
Remove genericity, x64 and renamed stuff As per discussion on the github issue, the following changes were made: * Project renamed from elevate to kitrap0d, implying that this is not intended to be a generic local priv esc exploit container. * Container DLL no longer generic, always calls the kitrap0d exploit. * Removal of all x64 code and project configurations. * Invocation of the exploit changed so that the address of the payload is passed in to the exploit entry point. The exploit is now responsible for executing the payload if the exploit is successful. This removes the possibility of the payload getting executed when the exploit fails. * Source moved to the appropriate CVE folder. * Binary moved to the appropriate CVE folder. * Little bit of source rejigging to tidy things up.
2013-11-14 03:17:07 +01:00
Use railties to load Metasploit::Credential correctly MSP-9606 In order to support Metasploit::Credential correctly, metasploit-framework needs to support Metasploit::Concern, which does all its magic using a Rails::Engine initializer, so the easiest path is to make metasploit-framework be able to use Rails::Engines. To make Rails::Engine use Rails::Engine, make a dummy Rails::Application subclass so that all the initializers will be run when anything requires msfenv.
2014-05-12 22:03:51 +02:00
# Rails log directory
/log
adding scenarios for booting msfconsole without a db
2014-08-20 18:02:11 +02:00
# Rails tmp directory
/tmp
Use railties to load Metasploit::Credential correctly MSP-9606 In order to support Metasploit::Credential correctly, metasploit-framework needs to support Metasploit::Concern, which does all its magic using a Rails::Engine initializer, so the easiest path is to make metasploit-framework be able to use Rails::Engines. To make Rails::Engine use Rails::Engine, make a dummy Rails::Application subclass so that all the initializers will be run when anything requires msfenv.
2014-05-12 22:03:51 +02:00
Remove genericity, x64 and renamed stuff As per discussion on the github issue, the following changes were made: * Project renamed from elevate to kitrap0d, implying that this is not intended to be a generic local priv esc exploit container. * Container DLL no longer generic, always calls the kitrap0d exploit. * Removal of all x64 code and project configurations. * Invocation of the exploit changed so that the address of the payload is passed in to the exploit entry point. The exploit is now responsible for executing the payload if the exploit is successful. This removes the possibility of the payload getting executed when the exploit fails. * Source moved to the appropriate CVE folder. * Binary moved to the appropriate CVE folder. * Little bit of source rejigging to tidy things up.
2013-11-14 03:17:07 +01:00
# ignore release/debug folders for exploits
external/source/exploits/**/Debug
external/source/exploits/**/Release
Update .gitignore to avoid Meterpreter bins
2014-06-20 18:57:59 +02:00
# Avoid checking in Meterpreter binaries. These are supplied upstream by
Add the POSIX binaries to the ignore list Now that the POSIX bins are in the metasploit-payloads gem, we can make sure that we don't accidentally include them in future commits by adding them to gitignore.
2015-05-06 23:25:24 +02:00
# the metasploit-payloads gem.
Ignore all the DLLs We don't keep any meterpreter DLLs in the main repo now, so this changes the ignore to make sure nothing goes in.
2015-03-20 04:12:48 +01:00
data/meterpreter/*.dll
Add .php and .py meterpreter excludes to gitignore
2015-12-08 07:59:57 +01:00
data/meterpreter/*.php
data/meterpreter/*.py
Add the POSIX binaries to the ignore list Now that the POSIX bins are in the metasploit-payloads gem, we can make sure that we don't accidentally include them in future commits by adding them to gitignore.
2015-05-06 23:25:24 +02:00
data/meterpreter/*.bin
remove android meterpreter bins, update to payloads 1.0.2 This switches us to using the Android payload files from the metasploit-payloads gem
2015-05-29 00:34:34 +02:00
data/meterpreter/*.jar
Add the POSIX binaries to the ignore list Now that the POSIX bins are in the metasploit-payloads gem, we can make sure that we don't accidentally include them in future commits by adding them to gitignore.
2015-05-06 23:25:24 +02:00
data/meterpreter/*.lso
remove android meterpreter bins, update to payloads 1.0.2 This switches us to using the Android payload files from the metasploit-payloads gem
2015-05-29 00:34:34 +02:00
data/android
data/java
Update .gitignore to avoid Meterpreter bins
2014-06-20 18:57:59 +02:00
# Avoid checking in Meterpreter libs that are built from
# private source. If you're interested in this functionality,
use https for metaploit.com links
2017-07-24 15:26:21 +02:00
# check out Metasploit Pro: https://metasploit.com/download
Add wildcards to gitignore for extensions
2014-06-24 19:19:59 +02:00
data/meterpreter/ext_server_pivot.*.dll
Also .gitignore the source directory for metakitty
2014-12-03 23:12:30 +01:00
# Avoid checking in metakitty, the source for
# https://rapid7.github.io/metasploit-framework. It's an orphan branch.
/metakitty
ignore .vagrant directory.
2016-02-10 05:48:12 +01:00
.vagrant
Dockerfile and Docker Compose for Metasploit Adds a basic Dockerfile and docker-compose config. `docker-compose.yml` adds a named volume for postgres so data should persist. `$HOME/.msf4` will be mounted to `/root/.msf4` by default. port 4444 is exposed by default Basic Usage: docker/bin/msfconsole docker/bin/msfvenom
2016-07-18 20:38:57 +02:00
# local docker compose overrides
docker-compose.local*
more docker work
2017-11-28 21:35:20 +01:00
.env
move common json-rpc bits to a library
2017-04-01 13:25:51 +02:00
# Ignore python bytecode
*.pyc
trying rspec-retry
2017-06-20 21:02:32 +02:00
rspec.failures
Ignore base metadata store file
2017-11-21 16:57:41 +01:00
#Ignore any base disk store files
Add tests for aux and exploit cmd_check and cmd_run
2021-06-25 12:46:44 +02:00
db/modules_metadata_base.pstore