Remove DeclaredHandler to prevent accidental internal discovery #11
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.
The
DeclaredHandlerhas become a liability. Because class, interface, and enum names are represented as strings, we run the risk of the library "helpfully" identifying a piece of user input as an internal system part.If a user happens to input a string that matches an internal class or enum name, the stringifier would automatically confirm its existence by applying the specialized formatting. This creates an information leakage vulnerability where an outsider could map out our application's internal architecture simply by guessing names.
By removing this handler, we ensure that a string is treated just as a string. This follows our recent "secure-by-default" trend seen in the
CallableStringifierchanges: we are prioritizing the privacy of the application's internal blueprint over the convenience of automatic type detection.