Open
Conversation
The possibility to add arbitrary data to a Media Signing SEI generates an attack vector. Therefore, that specific type is removed from the specification. If a vendor would like to add some metadata and have it signed, that data shall be put in a separate SEI of type user data unregistered with a different UUID (44959c31-e3f3-4aeb-8b4c-5e3a865801fc).
Member
|
Do not see any value to create yet another fixed UUID. Suggest to either define a generic mechanism which SEIs are signed or keep as is. |
Contributor
Author
I agree with you. That was my initial thought as well. Then I started to think about what is the simplest way for a device to do and control this, which in my opinion would be to "add it the way you want as long as Media Signing knows about the UUID". I like keeping it all within the same SEI Media Signing UUID better, even if it adds a little bit of complexity to the device. |
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
2 participants
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 possibility to add arbitrary data to a Media Signing SEI generates an attack vector. Therefore, that specific type is removed from the specification.
If a vendor would like to add some metadata and have it signed, that data shall be put in a separate SEI of type user data unregistered with a different UUID (44959c31-e3f3-4aeb-8b4c-5e3a865801fc).