Feature obfuscator option #184
Closed
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
… the main build unless this is of interest. Fully working. Also adds tests.
|
I am 💯 ok with this, philosophically. My goal was to help further along obfuscated/encrypted sticky cookies, and #216 does that just fine. Thank you @jbdoumenjou & friends. Feel free to close this PR after #216 is accepted and committed. |
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.
Cousin to #156 implemented as a CookieOption. In separate commits implements a Hex-based Obfuscator, and implements an AES-based Obfuscator in a _test (with tests) to show how that can work.