FIX update example conf file so pyrit_scan doesn't fail out of the box#2046
Open
behnam-o wants to merge 1 commit into
Open
FIX update example conf file so pyrit_scan doesn't fail out of the box#2046behnam-o wants to merge 1 commit into
behnam-o wants to merge 1 commit into
Conversation
romanlutz
changed the title
adrian-gavrila
approved these changes
Jun 19, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The example conf file is missing an initializer that
pyrit_scan --start-serverdepends on. So when a user uses the example conf and run pyrit_scan, they get this error:Error executing initializer LoadDefaultDatasets: AttackTechniqueRegistry is empty. Register attack technique factories before executing scenarios — for example by running the default ScenarioTechniqueInitializer (pyrit.setup.initializers.components.scenario_techniques), running another initializer that calls AttackTechniqueRegistry.register_from_factories(...), or registering factories directly via AttackTechniqueRegistry.get_registry_singleton().