Configuration
Pwnity uses a local-first, session-based configuration. All settings are stored in etc/config.json. This approach follows our "No database, no dumps, no pain" philosophy.
Global Settings
The GLOBAL section manages core application behavior.
DEBUG_LEVEL: Controls log verbosity (DEBUG, INFO, WARNING, ERROR).HISTORY_FILE: Path to your CLI command history.LOOT_TYPES: Defines valid categories for thelootcommand (e.g., credentials, tokens, artifacts).
Directory Structure (DIRS)
Pwnity is ultra-portable because it maps all its logical objects to local directories.
PRESETS: Saved session templates.TARGETS: JSON objects containing target metadata and scan results.WORDLISTS: References to your local wordlist files.REPORTS: The central storage for all notes and findings.
Heartbeat & Stability
The HEARTBEAT section controls how Pwnity monitors background jobs and target responsiveness.
MIN_DELAY_SECONDS: The minimum interval for health checks.MAX_DELAY_SECONDS: The maximum interval for jittered health checks.
Proxy Configuration
Pwnity supports per-session proxy settings, often using proxychains as a wrapper.
ENABLED: Global toggle for proxy support.WRAPPER_COMMAND: The binary used to wrap tool execution (e.g.,proxychains).WRAPPER_NEEDS_SUDO: Set totrueif your proxy wrapper requires elevated privileges.
Customization (COLORS)
You can customize the CLI's visual output by modifying the ANSI color codes in the COLORS section of the config file.
TIP
Since Pwnity stores everything in JSON, you can easily sync your
etc/ and data directories with any backup tool or git repository for instant cross-device portability.