Add option for custom scripts directory #55
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
1 participant
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 PR adds an option for providing a custom scripts directory. This gives the user a lot of freedom since they can use more sophisticated unpinning scripts and additionally, for instance, even setup a proxy using a Frida script.
Btw, some of the built-in (i.e., httptoolkit's) unpinning scripts may not work, as some hooks assume that the custom SSL certificate to accept is stored inside the
CERT_PEMvariable; see here. This is probably also the reason why unpinning doesn't work for some apps, as mentioned in #36. Thus, maybe it makes sense to add a default certificate in another PR?