Pentest Tool Setup

Pentest Tool Installation and Troubleshooting

This skill outlines a general workflow for installing and troubleshooting penetration testing tools, particularly focusing on Ruby-based tools and common dependency/permission issues.

Workflow

1. Check for existing installation (package manager first):

• Before attempting manual installation, check if the tool is available via your system's package manager (e.g., brew on macOS, apt on Ubuntu).
• Example: brew install

1. Web Search for Installation Instructions:

• If the tool is not found via package manager, perform a web search for "how to install ".
• Prioritize official GitHub repositories or documentation.

1. Clone the Repository (if applicable):

• For tools distributed via source code, clone the GitHub repository:

git clone

• Navigate into the cloned directory:

cd

1. Install Dependencies:

• Identify the dependency management system (e.g., RubyGems with Bundler for Ruby, pip for Python, npm/yarn for Node.js).
• Ruby/Bundler Specifics:
• The bundle install command often fails due to sudo requirements or system Ruby versions.
• Pitfall: bundle install without --path can attempt to write to system gem directories, requiring sudo. If sudo is not available or not desired (as in an automated agent context), this will fail.
• Workaround: Install gems to a user-specific directory using bundle install --path vendor/bundle. This creates a vendor/bundle directory within the project, containing all dependencies.
• Pitfall: Missing system libraries (e.g., libyaml for psych gem).
• Workaround: Install the missing system library using brew (macOS) or apt (Ubuntu): brew install libyaml. After installing the library, retry bundle install --path vendor/bundle.

1. Execute the Tool:

• If dependencies were installed to a local path (e.g., vendor/bundle), you often need to use bundle exec to ensure the tool runs with the correct local dependencies.
• Example: bundle exec ./
• Pitfall: Running the tool without bundle exec might lead to "command not found" or missing dependency errors if system-wide gems are not configured correctly or are outdated.

1. Manage Output:

• When directing output to a file, ensure the target directory exists and the paths are correct relative to the current working directory.
• Example: bundle exec ./whatweb -q > ../output_directory/result.txt (if running from tool directory and output directory is one level up).

Pitfalls

• sudo requirements: Avoid sudo where possible by installing dependencies to user-specific paths (bundle install --path vendor/bundle, pip install --user).
• Missing system libraries: Error messages often indicate missing .h files or libraries. Use brew or apt to install these.
• Incorrect execution context: For Ruby tools with local vendor/bundle installations, always use bundle exec to ensure the correct environment.
• Relative paths: Be mindful of your current working directory when specifying input/output file paths.

Verification

• After installation, run the tool with a simple command (e.g., --help or against a known-good target) to ensure it executes without errors.

Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

• Author: Wang200935
• Source: Wang200935/security-agent-skills
• License: MIT

Install and usage instructions live in the source repository linked above.