Expand the security considerations section #329
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
Addresses #281. * Explain why TTML2's security considerations apply * Explain how XML attack risks are addressed * Describe subresource integrity attack and potential mitigation * Further constrain document constraints by expanding `#serialization` to prohibit Byte Order Mark (BOM) and DTD references.
This was referenced Nov 6, 2025
Reference Document Type Declaration, Entity Declarations, Entity references and predefined entities. This change also prohibits both internal DTDs and external ones.
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.
Addresses #281.
#serializationto prohibit Byte Order Mark (BOM) and DTD references.Preview | Diff