[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]
Re: [tor-bugs] #20792 [Applications/Tor Browser Sandbox]: Add more options for changing the install process behavior
#20792: Add more options for changing the install process behavior
----------------------------------------------+-------------------------
Reporter: yawning | Owner: yawning
Type: enhancement | Status: new
Priority: Medium | Milestone:
Component: Applications/Tor Browser Sandbox | Version:
Severity: Normal | Resolution:
Keywords: | Actual Points:
Parent ID: | Points:
Reviewer: | Sponsor:
----------------------------------------------+-------------------------
Comment (by yawning):
Replying to [comment:1 arma]:
> The bundle, where your initial download is large and then it just works,
seems like the more pleasant approach in the face of a complicated
network.
I basically agree here.
To make this happen:
* There to be a consistent, documented and maintained method to extract
information from an installed bundle to replace the metadata acquired
from the `downloads.json` file on first install.
`{"version":"6.5.2","architecture":"linux64","channel":"release","locale
":"en-US"}`
* Write code to use files at a fixed location relative to the `sandboxed-
tor-browser`
binary as the tarball/signature for the install.
* Modify the descriptors to package the current bundle and signature with
`sandboxed-tor-browser`.
nb:
* "You can parse <random Javascript files in the bundle" is not
acceptable.
* "Just include a pre-generated manifest" is also not acceptable.
* I kind of want the metadata to be in a predictable location in bundles
anyway,
because it will be covered by the bundle's signature(s).
--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/20792#comment:2>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online
_______________________________________________
tor-bugs mailing list
tor-bugs@xxxxxxxxxxxxxxxxxxxx
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs