Trac issueshttps://gitlab.torproject.org/legacy/trac/-/issues2020-06-16T01:28:32Zhttps://gitlab.torproject.org/legacy/trac/-/issues/32204Create either a query or event-based API to allow controllers (particularly T...2020-06-16T01:28:32ZrichardCreate either a query or event-based API to allow controllers (particularly Tor Browser) to reliably get circuit informationCurrently we can not get the address or type of a bridge by id/fingerprint if the bridge entry in torrc does not have the fingerprint string provided. This info is needed for the circuit display in Tor Browser, which currently just displ...Currently we can not get the address or type of a bridge by id/fingerprint if the bridge entry in torrc does not have the fingerprint string provided. This info is needed for the circuit display in Tor Browser, which currently just displays 'Bridge' without the address or type information.
Tor Browser currently gets the circuit display information by first requesting the circuit for a given first-party domain/nonce pair. This returns an array of fingerprints. We then get the list of bridges stored in the torrc file via `GETCONF bridge`. We compare each bridge's id to each node in the circuit. If a match if sound we know the node is a bridge and we display its information. Otherwise, we assume it is a relay and we query the information from tor via `GETINFO ns/id/$fingerprint`.
With the change in #32125 we now infer that if the GETINFO call fails, it's because the id we've received is actually a Bridge whose info we do not know.
Some possible options:
- Tor updates the torrc with the Bridge's fingerprint once it is known. Tor Browser's logic doesn't change but there will be a window when a user looking at the circuit display will just see 'Bridge' rather than the full set of information.
- Tor adds a new query API that allows us to get Bridge information in a similar fashion to how we currently get relay information. The repeated GETCONF for bridges goes away and we now for each id in the circuit, we just try querying bridge info and if that fails we then query relay info.
- Tor Browser listens for the 'figured out the fingerprint for this bridge event' (which I believe currently just logs?) and maintains some in-memory map/cache of fingerprint to { type, ip, geolocation }. I'd really rather not do this.
- Add a 'verbose' circuit query API, where we just provide the domain/nonce pair and you give us the required data all at once. This would simplify Tor Browser code and would require less back-and-forth between tor and Tor Browser.Tor: unspecifiedhttps://gitlab.torproject.org/legacy/trac/-/issues/33117Tor Launcher Issues2020-06-13T10:53:50ZAntonelaantonela@torproject.orgTor Launcher IssuesParent ticket for known tor-launcher issues which apply into s30 scopeParent ticket for known tor-launcher issues which apply into s30 scopehttps://gitlab.torproject.org/legacy/trac/-/issues/32547Set up default bridge at the University of Minnesota2020-06-16T01:09:56ZPhilipp Winterphw@torproject.orgSet up default bridge at the University of MinnesotaA research group at the University of Minnesota generously agreed to running a default bridge for us. Let's use this ticket to coordinate the process of adding it to Tor Browser.A research group at the University of Minnesota generously agreed to running a default bridge for us. Let's use this ticket to coordinate the process of adding it to Tor Browser.Philipp Winterphw@torproject.orgPhilipp Winterphw@torproject.orghttps://gitlab.torproject.org/legacy/trac/-/issues/32205Implement tor-button changes needed to take advantage of improved bridge info...2020-06-16T01:28:32ZrichardImplement tor-button changes needed to take advantage of improved bridge info query API in torSome changes to tor-button will be needed to properly display the information of user-provided bridges without a fingerprint in the circuit display. Whichever path outlined in #32204 is done, the work needed in Tor Browser is a minimal a...Some changes to tor-button will be needed to properly display the information of user-provided bridges without a fingerprint in the circuit display. Whichever path outlined in #32204 is done, the work needed in Tor Browser is a minimal amount of javascript in tor-button.https://gitlab.torproject.org/legacy/trac/-/issues/32111Adding your own custom bridges generates a parsing error2020-06-16T01:08:28ZGusAdding your own custom bridges generates a parsing errorIn Tor Browser alpha (9.0a8), if I add a custom bridge starting with Bridge:
> Bridge obfs4 IP:Port cert
It gives me a parsing error:
> 10/16/19, 13:22:41.785 [WARN] Error parsing Bridge address 'obfs4'
But it works if I add directl...In Tor Browser alpha (9.0a8), if I add a custom bridge starting with Bridge:
> Bridge obfs4 IP:Port cert
It gives me a parsing error:
> 10/16/19, 13:22:41.785 [WARN] Error parsing Bridge address 'obfs4'
But it works if I add directly:"obfs4 IP:Port cert..."
In Tor Browser stable it works both ways (Bridge and only obfs4).https://gitlab.torproject.org/legacy/trac/-/issues/32105bridges@torproject.org don't respond2020-06-13T18:29:51ZTracbridges@torproject.org don't respondI use Gmail to send email to bridges@torproject.org, but it doesn't respond.
**Trac**:
**Username**: mh828I use Gmail to send email to bridges@torproject.org, but it doesn't respond.
**Trac**:
**Username**: mh828Philipp Winterphw@torproject.orgPhilipp Winterphw@torproject.orghttps://gitlab.torproject.org/legacy/trac/-/issues/31427Update BridgeDB's documentation2020-06-13T18:29:43ZPhilipp Winterphw@torproject.orgUpdate BridgeDB's documentationParts of BridgeDB's documentation is out-of-date. We should:
* Update the AUTHORS file.
* Update HACKING.md.
* Update contact info and the trac URL to file bugs.
I'll push a patch set in a minute.Parts of BridgeDB's documentation is out-of-date. We should:
* Update the AUTHORS file.
* Update HACKING.md.
* Update contact info and the trac URL to file bugs.
I'll push a patch set in a minute.Philipp Winterphw@torproject.orgPhilipp Winterphw@torproject.orghttps://gitlab.torproject.org/legacy/trac/-/issues/30941Need better instructions for requesting bridges via email2020-06-13T18:29:35ZPili GuerraNeed better instructions for requesting bridges via emailFor bridges obtained via email by emailing bridges@ it's not clear how/where to request bridges via email.
E.g the bridges.tpo website simply says to email bridges@ to get bridges
Emailing that address gives you a number of commands bu...For bridges obtained via email by emailing bridges@ it's not clear how/where to request bridges via email.
E.g the bridges.tpo website simply says to email bridges@ to get bridges
Emailing that address gives you a number of commands but doesn't specify where to send the commands (email subject, body...) I tried both and wasn't able to get it to work.
It also specifies that you can combine commands but it doesn't give any examples or indication of how to do so.
This was raised by a user and I also couldn't figure it out after trying for about 5 minutes :/Philipp Winterphw@torproject.orgPhilipp Winterphw@torproject.orghttps://gitlab.torproject.org/legacy/trac/-/issues/27476Remove gap between Tor Launcher window and main browser window2020-06-16T00:50:01ZArthur EdelsteinRemove gap between Tor Launcher window and main browser windowRight now, the Tor Launcher runs, and takes seconds or minutes to complete. The Tor Launcher window, though it says "Tor Browser" on the first screen is not recognizably a web browser, which may be confusing or scary to first-time users....Right now, the Tor Launcher runs, and takes seconds or minutes to complete. The Tor Launcher window, though it says "Tor Browser" on the first screen is not recognizably a web browser, which may be confusing or scary to first-time users.
Then the Tor Launcher window disappears, and then, before a browser window appears, there is a gap of varying length where no window is visible at all. On slow computers, this gap can be as much as tens of seconds and during that time there is no easy way to tell that Tor Browser is still running.
Often users, mistakenly guessing that Tor Browser has crashed, will double-click the Tor Browser app icon a second time and get messages like "Tor Browser is already running, but is not responding" or "Tor unexpectedly exited".
How can we solve this problem? I can think of a few possible solutions:
1. Don't hide the Tor Launcher window until the main browser window is visible. (Build the browser window hidden during the launch process so that it can appear fast as soon as the launch process is done.)
2. Show the main browser window below the Tor Launcher window while it launching process is running. Keep the Tor Launcher window modal (always on top) until it is finished.
3. Embed the Tor Launcher UI in the main browser window. Allow the user to enter a URL in the URL bar even before Tor is fully launched.
I favor (3) as having the best UX. But it is also the most difficult to implement.https://gitlab.torproject.org/legacy/trac/-/issues/24452Firewall option is visible behind Tor Network Settings... but not during star...2020-06-13T17:43:52ZGeorg KoppenFirewall option is visible behind Tor Network Settings... but not during start-upnicoo got confused by firewall options not being visible during start-up but behind the Tor Network Settings... option. I think they are right we should avoid that mismatch.nicoo got confused by firewall options not being visible during start-up but behind the Tor Network Settings... option. I think they are right we should avoid that mismatch.Kathleen BradeKathleen Bradehttps://gitlab.torproject.org/legacy/trac/-/issues/23486nice icons for the progress bar2020-06-13T17:43:47ZIsabela Fernandesnice icons for the progress barTicket asking if Antonela could make beautiful icons for us to use at the progress bar, representing different steps of configuration to connect to Tor network.
Attached is a screenshot of the current ones we have in the mock for refere...Ticket asking if Antonela could make beautiful icons for us to use at the progress bar, representing different steps of configuration to connect to Tor network.
Attached is a screenshot of the current ones we have in the mock for reference.Kathleen BradeKathleen Bradehttps://gitlab.torproject.org/legacy/trac/-/issues/11698Decide how to incorporate Tor Browser Manual pages into Tor Browser2020-06-15T23:34:47ZMatt PaganDecide how to incorporate Tor Browser Manual pages into Tor BrowserWe want the Tor Browser User Manual to ship with Tor Browser. We need to decide how the manual will be presented to the user, including what file format the user will be accessing.We want the Tor Browser User Manual to ship with Tor Browser. We need to decide how the manual will be presented to the user, including what file format the user will be accessing.