Draft
Conversation
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
1 participant
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.
Note
This is a simpler alternative to #8616. Creating this PR as a draft for the sake of discussion.
If a CAA record contains any parameters which we don't recognize, we shouldn't simply ignore them. The parameters are likely there because the user wants some particular protection, and we might be violating their security expectations by ignoring that parameter.
This includes simply mis-capitalized versions of recognized parameters, such as "AccountURI" or "validationMethods". We do not see these mis-capitalizations in practice, so we do not expect this to be a breaking change for any existing users. By putting this in place now, we will prevent any future proliferation of accidentally-miscapitalized parameters.
Fixes #8614