Communities

Writing
Writing
Codidact Meta
Codidact Meta
The Great Outdoors
The Great Outdoors
Photography & Video
Photography & Video
Scientific Speculation
Scientific Speculation
Cooking
Cooking
Electrical Engineering
Electrical Engineering
Judaism
Judaism
Languages & Linguistics
Languages & Linguistics
Software Development
Software Development
Mathematics
Mathematics
Christianity
Christianity
Code Golf
Code Golf
Music
Music
Physics
Physics
Linux Systems
Linux Systems
Power Users
Power Users
Tabletop RPGs
Tabletop RPGs
Community Proposals
Community Proposals
tag:snake search within a tag
answers:0 unanswered questions
user:xxxx search by author id
score:0.5 posts with 0.5+ score
"snake oil" exact phrase
votes:4 posts with 4+ votes
created:<1w created < 1 week ago
post_type:xxxx type of post
Search help
Notifications
Mark all as read See all your notifications »
Q&A

Welcome to Software Development on Codidact!

Will you help us build our independent community of developers helping developers? We're small and trying to grow. We welcome questions about all aspects of software development, from design to code to QA and more. Got questions? Got answers? Got code you'd like someone to review? Please join us.

Extracting Firefox Local Data

+1
−0

How does one parse/decode/extract information stored by a web page in Firefox's browser local storage without the browser?

So far, I've worked out that the data lives at ~/.mozilla/firefox/${profile}/storage/default/${site}/ls/data.sqlite, where the site looks something like https+++software.codidact.com. Because the browser locks the database at least when the page is open, I copy it off to a temporary version.

SQLite3 then shows two tables, database that mostly only describes the site, and data which holds what we find under Developer Tools/Storage/Local Storage/(relevant URL). Querying SELECT value FROM data WHERE key = 'whateverKeyWeCareAbout' gives...something.

So far, so good.

However, the "something" that we get from the value column might come through as plain JSON - it looks like this happens when the browser serializes a smaller object - or it might come through as something more complicated, which resembles small fragments of the expected JSON interspersed with opaque binary sequences. The latter is the concern, here.

The site that interests me happens to be Open Source, so I checked to see if they maybe used some bizarre encryption, but no, they store to local storage with localStorage.setItem(JSON.stringify(object)) from a single central utility function, so I can't pull the mechanism out of there.

I've seen suggestions that Firefox uses MessagePack for this storage, but the data doesn't seem to decode with that assumption. Another suggests that this might be the internal representation of the structured clone algorithm, but I couldn't find any corroboration for this or any code or tool to get a serialized form to verify it.

The ideal would be to run something like sqlite3 "copied-data.sqlite" "SELECT value FROM data WHERE key = 'whateverKeyWeCareAbout'" | tool-to-get-JSON | jq .field and use that further in a script. Though I'm open to almost anything that doesn't tie up the browser.

History
Why does this post require attention from curators or moderators?
You might want to add some details to your flag.
Why should this post be closed?

0 comment threads

0 answers

Sign up to answer this question »