Opened 3 years ago

Last modified 7 months ago

#18369 new defect

Linux Tor Browser should not store data in the Browser (application) directory

Reported by: mcs Owned by: mcs
Priority: Medium Milestone:
Component: Applications/Tor Browser Version:
Severity: Normal Keywords:
Cc: brade, gk, yawning, dgr Actual Points:
Parent ID: #20599 Points:
Reviewer: Sponsor:

Description

We want to move to a model on all platforms where user data is not stored in the application area. This is the Linux-specific ticket. See #13252 for the original, Mac-specific ticket.

Child Tickets

Change History (6)

comment:1 Changed 3 years ago by gk

Cc: gk added

comment:2 Changed 2 years ago by mcs

See the comment thread here for another problem this will solve:
https://blog.torproject.org/blog/tor-browser-602-released#comment-187765

comment:3 Changed 2 years ago by mcs

Parent ID: #20599

comment:4 Changed 2 years ago by mcs

See #20497 for a related ticket.
Also, if there is a chance that the user data might be stored in a shared location such as the user's home directory, then we need to account for the last issue raised by Arthur in ticket:13252#comment:57 after all, i.e., we may need to embed the app path in the update directory (like we do on OSX) in order to ensure that the update history is partitioned.

comment:5 Changed 2 years ago by yawning

Cc: yawning added

Under this model, how does updating work? If it moves beyond "Download the MAR and update it like upstream firefox", then I'd need documentation on how to replicate the other steps for the whole "the sandboxing helper needs to handle installation/updates" use case.

Something I can set at runtime to force existing behavior would also work I guess...

Last edited 2 years ago by yawning (previous) (diff)

comment:6 Changed 7 months ago by gk

Cc: dgr added

I think it will solve #25663 as well where corrupted downloads during updates got reported.

Note: See TracTickets for help on using tickets.