Adds an Obfuscator interface, and implements a default GIGO obfuscator #156
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
|
Also, if it's of interest, I have sample Obfuscators using Hex encoding, SHA3 hashing, and AES-GCM. 🤷♂️ I was bored. :) |
|
I was wondering if anyone had any feedback on this? I'm open to changes or even new direction. This has been used (with a couple different Obfuscators) under production loads for a while now. I'd like to evolve it to a point to be accepted, so I can stop maintaining a branched fork for the downstream users. @ |
|
I've re-implemented the Obfuscator as a CookieOption, which you implemented since my initial PR. Maybe more palatable? Feedback would be appreciated. I'd rather not maintain and update a fork, but this is used pretty heavily. |
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.
Implements the Obfuscator talked about in #109 to allow users to resolve the concerns with #107. This is a drop-in replacement with a new constructor "NewStickySessionWithObfuscator" to select a custom Obfuscator, while not impacting existing installs.