Opened 2 years ago

Closed 9 months ago

#20792 closed enhancement (wontfix)

Add more options for changing the install process behavior

Reported by: yawning Owned by: yawning
Priority: Low Milestone:
Component: Archived/Tor Browser Sandbox Version:
Severity: Normal Keywords:
Cc: arthuredelstein Actual Points:
Parent ID: Points:
Reviewer: Sponsor:

Description

sandboxed-tor-browser has no provisions for handling situations like:

  • The tor website is blocked, except "well, you can point it at an existing tor installation, and it will install over tor".
  • Distributing sandboxed-tor-browser accompanied by a bundle (ie: one larger download up front).

Both of these situations should be fixed somehow.

Child Tickets

TicketTypeStatusOwnerSummary
#22262enhancementclosedyawningTor Browser Sandbox should offer the possibility to download the Tor Browser from mirrors

Change History (7)

comment:1 Changed 22 months ago by 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.

Last edited 22 months ago by arma (previous) (diff)

comment:2 in reply to:  1 Changed 22 months ago by yawning

Replying to 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).

comment:3 Changed 22 months ago by arthuredelstein

Cc: arthuredelstein added

comment:4 Changed 21 months ago by yawning

Priority: MediumLow

Lowering the priority on UI/UX related tasks. The entire UI code needs to be taken out back behind a shed and shot, and not incrementally added to.

comment:5 Changed 20 months ago by yawning

I closed #20792 as a duplicate.

comment:6 Changed 16 months ago by yawning

Having more options when situations like #24270 pops up is also a good reason to consider something like this.

comment:7 Changed 9 months ago by yawning

Resolution: wontfix
Status: newclosed

This project is deprecated, and none of these will ever be fixed.

Note: See TracTickets for help on using tickets.