Add Support for Config File#11
Open
l33tluigi wants to merge 6 commits into
Open
Conversation
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
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.
This has been a very helpful tool, but to speed up operations from single commands and to improve opsec by not hitting every resource/client ID, this PR adds support for a
--configflag that accepts a sectioned config file. This allows operators to scope checks to a specific set of resources, client IDs, and user agents rather than the full built-in dictionaries. The config uses friendly names from the internal dictionaries (e.g.,Azure Graph API,Intune MAM,iPhone Safari), which are resolved to their values at runtime. Any entry not found in the dictionaries is treated as a custom value and labeled explicitly in output (e.g., Custom (some-value)) to avoid ambiguity when multiple custom values are present. ATotal combinationsline was also added so operators know exactly how many requests will be sent when execution begins.