uazo

> technically it would have to cover the current profile preferences only, right? the preferences seem to me to be saved in two files: - /data/data/org.bromite.bromite/app_chrome/Local State - /data/data/org.bromite.bromite/app_chrome/Default/Preferences In...

> Only the user can; other apps cannot tamper with these files. yes, but theoretically as usual. in any case we would open a "backdoor" that currently does not exist....

> If you can prove that other apps can break the sandbox > otherwise please do not spread misinformation. no, absolutely not what I want. what I think (and maybe...

> If you refer to some app circumventing SuperSU on an already-rooted phone: this is out of scope for this project I think of who has the rooted phone but...

the problem with that patch is how to encrypt the data .. otherwise it's fine > should we continue with this or first look into https://github.com/bromite/bromite/issues/244 (or similar)? every time...

> Either no encryption or ask user to provide one. yes, I have also seen the various ways already available in the code to encrypt the data, I just have...

we just need to understand which method to apply to encrypt the produced file, have you already seen if there is something available?

> is activated only during the official Chrome builds? no, backup_key is completely without references but, not working for google, i don't know exactly how they compile... > Also: have...

> I think it's worth restoring what has been deleted to see if it works. I wouldn't worry about that, I'd put a flag. > Let me know what you...

> But is it encrypted or not? the password [yes](https://source.chromium.org/chromium/chromium/src/+/main:components/password_manager/core/browser/login_database_posix.cc;) > Once the file would be created, would other apps be able to access it? only if you know the...