-
Notifications
You must be signed in to change notification settings - Fork 8
Feature/vplay 13092 migrate fragmentcollector hls header to std vector #1220
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
Merged
pstroffolino
merged 9 commits into
dev_sprint_25_2
from
feature/VPLAY-13092_Migrate_fragmentcollector_hls_header_to_std_vector
Mar 24, 2026
Merged
Changes from 7 commits
Commits
Show all changes
9 commits
Select commit
Hold shift + click to select a range
bcc9234
Resolve conflict in fragmentcollector_hls.cpp: use updated GetFile() …
DomSyna 9055736
VPLAY-13092 Migrate AampGrowableBuffers in fragmentcollector_hls.h to…
DomSyna bcdb02e
VPLAY-13092 Migrate AampGrowableBuffers in fragmentcollector_hls.h to…
DomSyna 6ec0d92
VPLAY-13092 Migrate AampGrowableBuffers in fragmentcollector_hls.h to…
DomSyna 92c2b2b
VPLAY-13092 Migrate AampGrowableBuffers in fragmentcollector_hls.h to…
DomSyna b129b85
VPLAY-13092 Migrate AampGrowableBuffers in fragmentcollector_hls.h to…
DomSyna cc641a5
Merge branch 'dev_sprint_25_2' into feature/VPLAY-13092_Migrate_fragm…
DomSyna 625c307
VPLAY-13092 Migrate AampGrowableBuffers in fragmentcollector_hls.h to…
DomSyna f481043
Merge branch 'dev_sprint_25_2' into feature/VPLAY-13092_Migrate_fragm…
DomSyna File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
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
Oops, something went wrong.
Oops, something went wrong.
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.
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.
TrackState::~TrackState()became empty. Previously it explicitly zeroedmDrmInfo.iv; with the destructor now empty, the IV bytes can remain in freed memory until overwritten. Please restore secure clearing of sensitive DRM fields (e.g., explicitly zeromDrmInfo.iv, ideally using a clearing routine that won’t be optimized out).Uh oh!
There was an error while loading. Please reload this page.
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.
If a bad actor can access the released memory to read the transient init vector data they can also read the data structure, which will be much easier to find. For it to be properly secure it would have to live in the TEE.
The Init vector is often in the clear, so not really that secret.