Opened 4 years ago

Last modified 20 months ago

#14383 new enhancement

finalize RecommendedTBBVersions format

Reported by: proper Owned by: tbb-team
Priority: Medium Milestone:
Component: Applications/Tor Browser Version:
Severity: Normal Keywords:
Cc: sukhbir, micahlee, adrelanos@…, gk Actual Points:
Parent ID: #14386 Points:
Reviewer: Sponsor:

Description

People use downloaders/scripts to Download TBB. (There is torbrowser-launcher as well as tb-updater and perhaps more.)

The problem is, the RecommendedTBBVersions format is currently undocumented and unfinalized. It changed very often in past and therefore broke these TBB downloaders. This is non-ideal. This is a feature request to finalize the RecommendedTBBVersions format to keep these downloaders functional.

Child Tickets

Change History (8)

comment:1 Changed 4 years ago by proper

comment:2 Changed 4 years ago by proper

Cc: adrelanos@… added
Parent ID: #14386

comment:3 Changed 4 years ago by gk

Cc: gk added

comment:4 Changed 4 years ago by gk

Marked #14739 as duplicate.

comment:5 Changed 4 years ago by evil

i support this ticket and i would like to help defining a usable API.

together with ilv and naif i'm implementing a /gettor functionality [1] for the tor2web project and this are the issues i've currently found that it would be good to discuss for the definition of RecommendedTBBVersions API.

1) Currently it's not possible to clearly discern which are the stable versions and which are the alpha versions;
2) Currently the API does not export any information about the language in which the TBB is available and an user that would like to know it would have to parse directly the repository HTML;
3) Currently the API does not clarify which are the operating systems for which each version is available in a usable way; in fact also on this currently the API currently mixes the version number with the name of the operating system causing need custom and possibly buggy parsing;
4) Currently the API does not export the link to the Browser binary that would be useful for implementing tb-update and checktor like functionalities; currently in all our projects we are composing languages we think exists plus the version plus the os and expecting the binary to be there;
5) As for 4) currently the API does not export the link to the browser binary signature.

[1] https://github.com/globaleaks/Tor2web-3.0/issues/168

comment:6 in reply to:  5 Changed 4 years ago by gk

Replying to evil:

i support this ticket and i would like to help defining a usable API.

together with ilv and naif i'm implementing a /gettor functionality [1] for the tor2web project and this are the issues i've currently found that it would be good to discuss for the definition of RecommendedTBBVersions API.

1) Currently it's not possible to clearly discern which are the stable versions and which are the alpha versions;

It is possible and even specified: https://gitweb.torproject.org/tor-browser-spec.git/tree/processes/VersionNumbers

comment:7 Changed 4 years ago by naif

related to #16551

comment:8 Changed 20 months ago by teor

Severity: Normal

Set all open tickets without a severity to "Normal"

Note: See TracTickets for help on using tickets.