Opened 7 years ago

Closed 2 years ago

#7583 closed defect (worksforme)

Distribute Tor Browser version and other information through consensus and internal mapaddress + JSON/XML object

Reported by: proper Owned by:
Priority: Medium Milestone: Tor: unspecified
Component: Applications/Tor Browser Version:
Severity: Normal Keywords: tor-client, needs-proposal, mike-0.2.5
Cc: proper, mikeperry, hellais, weasel, sysrqb, nickm, phobos Actual Points:
Parent ID: Points:
Reviewer: Sponsor:

Description

Related to #6546 "Replace check.tp.o with internal mapaddress + JSON/XML object".

You want to get ride of check.tpo entirely, right? So what is check.tpo used at the moment? Checks IP, Tor Browser version, some other information in multiple languages.

Replying to mikeperry:

https://gitweb.torproject.org/user/mikeperry/torspec.git/blob/mapaddress-check:/proposals/xxx-mapaddress-tor-status.txt

The design currently only solves checking the IP. Check.tpo would still be required for checking Tor Browser version and the other information. That's missing in the design.

Suggestion:
Distribute Tor Browser version and the other information together with the Tor consensus. Let Tor Button read it through internal mapaddress + JSON/XML object just like in #6546.

Tickets #5236 "Make a deb of the Torbrowser and add to repository" and #3994 "Get TorBrowser in Debian" would only solve the Linux issue and are totally unrealistic. 1 Therefore no alternative solution.

Thandy... How many more years will it be until it's ready? Therefore no alternative solution?

1 Disto policy is a blocker. Tor Browser is too much of a hack. Too much writing into the home folder. Distro policy wants to prevent code duplication and does forbid to write (the profile) into the home folder. The policy or packer advice is for such cases is "put the functionality upstream". Exactly this won't work either. Mozilla is generally disinterested takes ages to merge patches. Getting Tor Browser into Linux distros won't work.

Child Tickets

Change History (8)

comment:1 Changed 6 years ago by nickm

Milestone: Tor: 0.2.5.x-final

Important. Needs a milestone. Doesn't seem likely to make 0.2.4, given feature cutoff.

comment:2 Changed 6 years ago by nickm

Keywords: tor-client added

comment:3 Changed 6 years ago by mikeperry

Keywords: needs-proposal mike-0.2.5 added

comment:4 Changed 5 years ago by nickm

Milestone: Tor: 0.2.5.x-finalTor: 0.2.???

I'm calling this probably superseded by proposal 227. Mike, agree?

comment:5 Changed 3 years ago by teor

Milestone: Tor: 0.2.???Tor: 0.3.???

Milestone renamed

comment:6 Changed 3 years ago by nickm

Keywords: tor-03-unspecified-201612 added
Milestone: Tor: 0.3.???Tor: unspecified

Finally admitting that 0.3.??? was a euphemism for Tor: unspecified all along.

comment:7 Changed 2 years ago by nickm

Keywords: tor-03-unspecified-201612 removed

Remove an old triaging keyword.

comment:8 Changed 2 years ago by nickm

Component: Core Tor/TorApplications/Tor Browser
Resolution: worksforme
Severity: Normal
Status: newclosed

I believe we already replaced this with a couple of mechanisms, including prop227 (which afaik hasn't seen much use?) and the auto-updater.

Tor Browser folks, please reopen kick this back over to me if there's more to do in Tor here.

Note: See TracTickets for help on using tickets.