Profile peristency #11
Description
Background of fakebrowser
fakebrowser persists consistency attributes in a file named fakebrowser.env.json, which in theory should be tightly coupled to one single profile.
All evasions with added noise essentially rely on a "salt" [canvas ,audio,etc..], and such attribute must be persisted on a per-profile basis to ensure consistency across different session.
Data models
- Canvas salt
- System fonts
- ... TBD: append hereby data models
Profiles persistency
Chromium persists profile data in a local directory. Within the production state of the project, the browser runs in a stateless container that becomes stateful once it mounts a volume with the profile folder. We have already implemented such concept in k8rome