Adding proxies and verify parameters for TAXII Client
#73
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
…ctor to programatically define proxy information. These params will be passed to the TAXII client.
Cyb3rWard0g
approved these changes
Mar 30, 2024
|
Thank you for the contribution and taking the time to help with this issue!! :) |
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.
Adding proxies and verify parameters to the attack_api.py constructor to programmatically define proxy information. These params will be passed to the TAXII client.
proxies- See https://requests.readthedocs.io/en/latest/user/advanced/#proxiesverify- See https://requests.readthedocs.io/en/latest/user/advanced/#ssl-cert-verificationThese changes should be transparent to those that don't need to use custom proxy or SSL verify functionality.
Fixes #56