> On 8 Oct 2017, at 02:39, intrigeri <intrigeri@???> wrote:
>
> 2. Then we have two options:
>
> a) Directly save low-level Tor Browser settings in .js format in
> the persistent file, and ensure that 1. this persistent file is
> loaded when Tor Browser starts (rather easy, as your research
> shows); 2. any change applied by the user to the security slider
> settings is persisted in that file (a bit harder, probably this
> would require adding code to our tor-browser wrapper script).
This could cause issues when the Tor Browser team changes which
features are at which levels. They have a re-evaluation scheduled
based on recent Mozilla security issues.
> b) Save the desired security slider settings in a higher-level way,
> in non-JS format, e.g. TOR_BROWSER_SECURITY_SLIDER=$level.
> Then our tor-browser wrapper script could set
> extensions.torbutton.security_slider accordingly on Tor Browser
> startup, and after Tor Browser has exited it could persist the
> updated settings to that persistent config file.
>
> I'm not sure which is best.
T
