Report Realm stores the bundled parser could not decode - #2085
Merged
Conversation
The bundled realm_parser decodes Realm file format 24. On other layouts _extract_schema returns an empty class list rather than raising, so a store the parser cannot read and a store that is genuinely empty look the same in the output. In a forensic tool those lead to opposite conclusions. This artifact lists any .realm file that holds more than 1024 non-zero bytes and from which no classes were decoded, with its size, non-zero byte count and file format. It reports nothing about contents. Header Read separates a file whose header could not be read at all, which is how a whole-file encrypted store presents, from one whose header is readable but whose format the parser does not decode. On the tested extractions this surfaces a 5 MB file format 9 store and a 20 KB store with no readable header, neither of which appeared anywhere in the output before. Reported upstream as kalink0/crush-forensics issue 55. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
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.
The bundled
realm_parserdecodes Realm file format 24. On other layouts_extract_schemareturns an empty class list rather than raising, so a store the parser cannot read and a store that is genuinely empty look the same in the output. In a forensic tool those lead to opposite conclusions: one says the app stored nothing, the other says reach for another tool.This artifact lists any
.realmfile that holds more than 1024 non-zero bytes and from which no classes were decoded, with its size, non-zero byte count and file format. It reports nothing about contents. Header Read separates a file whose header could not be read at all, which is how a whole-file encrypted store presents, from one whose header is readable but whose format the parser does not decode.On the tested extractions this surfaces a 5 MB file format 9 store and a 20 KB store with no readable header, neither of which appeared anywhere in the output before. The threshold excludes uninitialised stores: the two reported here hold 1,662,831 and 4,133 non-zero bytes, an uninitialised one held 204.
Reported upstream as kalink0/crush-forensics#55.