[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]

[tor-bugs] #7583 [Tor]: Distribute Tor Browser version and other information through consensus and internal mapaddress + JSON/XML object



#7583: Distribute Tor Browser version and other information through consensus and
internal mapaddress + JSON/XML object
--------------------+-------------------------------------------------------
 Reporter:  proper  |          Owner:     
     Type:  defect  |         Status:  new
 Priority:  normal  |      Milestone:     
Component:  Tor     |        Version:     
 Keywords:          |         Parent:     
   Points:          |   Actualpoints:     
--------------------+-------------------------------------------------------
 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 [comment:22 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.

-- 
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/7583>
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