Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Adds an Obfuscator interface, and implements a default GIGO obfuscator #156

Closed
wants to merge 6 commits into from

Conversation

cognusion
Copy link
Contributor

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.

@cognusion
Copy link
Contributor Author

Also, if it's of interest, I have sample Obfuscators using Hex encoding, SHA3 hashing, and AES-GCM. 🤷‍♂️ I was bored. :)

@cognusion
Copy link
Contributor Author

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. @

@cognusion
Copy link
Contributor Author

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
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant