Handle malformed AndroidQF backups#824
Merged
Merged
Conversation
Contributor
|
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.
Malformed
backup.abfiles inside AndroidQF acquisitions could cause the wholecheck-androidqfscan to terminate while initializing the nested backup command. This treats malformed AndroidQF backups like missing backups: MVT logs a warning, skips backup modules, and continues running the rest of the acquisition checks.The standalone
check-backupcommand remains strict for malformed backup input. Header parsing is also defensive for incomplete Android Backup headers, so truncated files are handled cleanly instead of raising from parser internals.Fixes #823.