This works very similar in the IGNORE_THESE_MODULES, except that they can be manually installed and updated through the modules/update_installed. This could be for large applications that take substantial time, ones that require user interaction, or open up a number of ports and protocols on the system. This will ignore modules only when doing install_update_all which are used when you want to install all tools. The IGNORE_UPDATE_ALL_MODULES= config option can be found under config/ptf.config in the PTF root directory. This will ignore modules and not install them - everything is comma separated and based on name - example: modules/exploitation/metasploit,modules/exploitation/set or entire module categories, like /modules/code-audit/*,/modules/reporting/* IGNORE Modules from Update/Install All The IGNORE_THESE_MODULES= config option can be found under config/ptf.config in the PTF root directory. This will install Metasploit first or ensured its installed first prior to installing the application. TOOL_DEPEND="modules/exploitation/metasploit" This will force PTF to install the required tool first, then install the module that requires it. You can add in the module TOOL_DEPEND="modules/exploitation/metasploit,module/exploitation/set" and multiple other tools if there is a tool required to be installed prior to installing the tool. require tools such as the Metasploit Framework. Use modules/password-recovery/johntheripper If you're running ptf in an automatic build, you can use a heredoc so you don't have to interactively type the modules you wish to install. ptf -update-all and it will automatically update everything for you without having to go into the framework. For example LAUNCHER="msfconsole,msfvenom". In order to add multiple launchers, simply put a, between them. For example, for Metasploit you may want msfconsole, msfvenom, etc. You can have multiple launchers for an application. All files will still be installed under the appropriate categories, for example /pentest/exploitation/setoolkit however an automatic launcher will be created. In the setoolkit example, when run - PTF will automatically create a file under /usr/local/bin/setoolkit so you can launch SET from anywhere by simply typing setoolkit. If you add LAUNCHER="setoolkit" for example, PTF will automatically create a launcher for the tool under /usr/local/bin/. The flag LAUNCHER= in modules is optional. PTF requires python-pexpect in order to work appropriately.ĭESCRIPTION="This module will install/update the Browser Exploitation Framework (BeEF)"ĪFTER_COMMANDS="cd "įor AFTER_COMMANDS that do self install (don't need user interaction). It's super simple to configure and add them and only takes a few minute. We want new tools added to the github repository. The ultimate goal is for community support on this project. We commonly see internally developed repos that you can use as well as part of this framework. Since this is a framework, you can configure and add as you see fit. PTF simplifies installation and packaging and creates an entire pentest framework for you. Everything is organized in a fashion that is cohesive to the Penetration Testing Execution Standard (PTES) and eliminates a lot of things that are hardly used. PTF attempts to install all of your penetration testing tools (latest and greatest), compile them, build them, and make it so that you can install/update your distribution on any machine. We have those "go to" tools that we use on a regular basis, and using the latest and greatest is important. As pentesters, we've been accustom to the /pentest/ directories or our own toolsets that we want to keep up-to-date all of the time. The PenTesters Framework (PTF) A TrustedSec Project - Copyright 2022 Written by: David Kennedy Twitter: PenTesters Framework (PTF) is a Python script designed for Debian/Ubuntu/ArchLinux based distributions to create a similar and familiar distribution for Penetration Testing.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |