Read Chromium tab restore files and report their navigation entries - #1309
Merged
Conversation
Adds a reader for the SNSS session files Chromium browsers write as Sessions/Tabs_<number>, and two artifacts over it: the navigation entries each tab was holding, with the address, page title, visit time and HTTP status, and the entry each tab was sitting on with the timestamp the browser stored when it closed. The framing was derived from the files, which tile to their exact byte length, and the command ids and the navigation entry field order come from Chromium. Every entry on the tested images consumed its record exactly. One path pattern covers Chrome, Brave and Edge because they share the app_chrome layout, and a Browser column attributes each row to the package it was found under. sample_data measured on 23 Android corpora. Co-Authored-By: Claude Opus 5 <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.
Adds a reader for the SNSS session files Chromium browsers write as Sessions/Tabs_, which nothing read before, and two artifacts over it.
The framing was derived from the files themselves and tiles to their exact byte length. The command ids and the navigation entry field order come from Chromium, in tab_restore_service_impl.cc and serialized_navigation_entry.cc. Every entry on the tested images consumed its record exactly, which is what shows the field order is right; a command id Chromium does not define is left as stored.
One pattern covers Chrome, Brave and Edge because they share the app_chrome layout, and a Browser column attributes each row to the package the file sits under. The reader has known-answer tests, including one for the four byte alignment that a length-only reader gets wrong. Measured on 23 Android corpora: 137 navigation entries and 58 tab records across 13 of them.
🤖 Generated with Claude Code