Auto-port 4.1: Marshalling: Explicit document security requirements#16754
Merged
Conversation
Motivation: When unmarshal pojos it is important to configure things strictly enough to not fall into security problems. Let's add some docs related to this so the end-user is aware of it. Modifications: Add javadoc that mention the requirement of strict configuration Result: Highlight to users the security concerns (cherry picked from commit 81db267)
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
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.
Auto-port of #16752 to 4.1
Cherry-picked commit: 81db267
Motivation:
When unmarshal pojos it is important to configure things strictly enough to not fall into security problems. Let's add some docs related to this so the end-user is aware of it.
Modifications:
Add javadoc that mention the requirement of strict configuration
Result:
Highlight to users the security concerns