Skip to content

Configuration

Pyro57000 edited this page May 20, 2025 · 1 revision

Initial configuration

The initial configuration is generated when you first run the tool. It will follow an install script that will prompt you for any information needed to generate the configuration files. It will also create the default project.

All files needed for the tool to run are stored in ~/.config/pyro_pentest_tool. The files include:

  • bell.mp3 This little mp3 file is used for the password spray help command. It will play when the observation window has expired.
  • conf This is the tool's main settings file, it stores the base paths for the files and notes folders for the current and upcoming projects, as well as the command used to execute your terminal running a specific command, the name of your template distrobox, the user@address string for your personal cracking rig if you have one (if you don't it'll be set to nobody@nothing), the location on that cracking rig for the rockyou.txt password file and one rule to rule them all rule file, whether you want to use fingerprint authentication inside your distroboxes, and your obsidian vault name. The format is setting_name:setting_data separated by new lines.
  • projects.conf this is where specific project settings are stored. After initial configuration this file will be populated with the default project's settings. New projects will be added by the tool when you create them or import them. The format is: customer:project_name:notes_folder_path:files_folder_path:Active_status:project_distrobox_name:project_stage projects are separated by newlines.
  • projects.conf.bkup this is a file that is automatically generated by the tool at run time, this ensures that if your project.conf file gets corrupted for any reason a semi recent backup is available to restore from. Manually restoring a corrupted projects.conf is possible, and not very hard (just follow the format) but kind of a pain.

If you need to change your settings at any time you can manually edit these. I do plan to include a confiuration management function within the tool itself eventually, but haven't gotten around to it yet.

Clone this wiki locally