Add User Agent rewrite functionality #61
Open
Conversation
This file contains 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
|
Pull request is aimed to address issue #59 |
|
Thanks for the PR @TinusGreen give me a few days to test things out and then I'll get it merged! |
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.
Using the default Python Requests package User Agent can be an IoC that can be used by blue teams to detect the use of SCCMHunter. This pull request introduces a new argument,
-uarwhich can be used to rewrite the User Agent.Taking the idea from ROADTools, a new dict with well known User Agents are provided, allowing users to choose a User Agent for rewrite. Once the argument is specified, all Python Requests will make use of the selected User Agent.
The feature works by defining an empty
headers = {}dict, which is then populated with aUser Agentvalue, if the-uarargument is used. A Ludus SCCM range was used ot verify the functionality and feature. While most commands were tested, coverage was not 100% due to the Ludus range not having the full configuration required to test every command of SCCMHunter.