Blog post - Working backwards from log4shell to see why we built lunasec #388
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
|
Nice Chris, let me do one more typo pass on that and maybe we can ship it..phew haha |
|
@freeqaz ready for merge or any changes you want to make |
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.
WIP but ready for first review. May need more references to Log4shell. This blog post walks the line between interesting story, advertisement, and documentation, and I'm not sure if it achieves all three in a clean way.
The focus on anything too technical here is pretty cursory. I think, in general, its enough to explain here that the product can protect you from RCE without getting into the implementation details of exactly how, such as auth-proxy strategies, "security levels", or multi-key encryption algorithms