-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
C2PA v2.1 Updates - BMFF hash v3 assertion #213
base: main
Are you sure you want to change the base?
Conversation
|
The BMFF hashing is quite complicated, so it would be crucial to get some sort of testing for this, covering:
|
|
||
if (!mdatBox) { | ||
throw new ValidationError(ValidationStatusCode.AssertionBMFFHashMismatch, this.sourceBox, 'mdat not found'); | ||
} | ||
|
||
// Start from the data portion of mdat (after 8-byte header) | ||
const dataOffset = mdatBox.offset + 8; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Should be able to use mdatBox.payloadOffset
for this
…ertion improvements
…on logic Add unit tests
…-v3.heic' in asset-reading tests.
0733b3d
to
acd6838
Compare
…handling and validation logic - Simplified exclusion sorting in AssertionUtils to only consider start positions. - Enhanced data processing in AssertionUtils to correctly handle offset markers and remaining data. - Updated BMFFHashAssertion to use mdatBox.payloadOffset for data retrieval, ensuring compliance with specifications. - Modified test cases to reflect changes in exclusion structure and improve validation checks for BMFF hash assertions.
No description provided.