[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]
[tor-bugs] #33939 [Applications/Tor Browser]: Decide which components of Fenix to rip out, disable, or use
#33939: Decide which components of Fenix to rip out, disable, or use
-------------------------------------+-------------------------------------
Reporter: gk | Owner: tbb-team
Type: task | Status: new
Priority: High | Milestone:
Component: Applications/Tor | Version:
Browser | Keywords: tbb-mobile,
Severity: Normal | TorBrowserTeam202004
Actual Points: | Parent ID: #33184
Points: | Reviewer:
Sponsor: |
-------------------------------------+-------------------------------------
One thing we are struggling with when trying to write proper patches for
building various parts of Fenix is that it's not clear yet which
components we want to rip out/disable/use.
E.g. there are a number of things we might want to rip out of `android-
components` (comment:4:ticket:33156) or maybe not, it's not clear. We have
already a separate bug (#33594) to figure out what we should do with
Glean.
So, in this ticket we should look over the various components involved and
decide
a) which to rip (fully) out at build time
b) disable at run time
and document the reasoning (maybe that could be part of our release prep
process documentation).
I think by default we should enable everything for usability reasons and
disable potentially fingerprinting/tracking features where we don't have
patches (yet) and rip out outright dangerous ones if we don't find a
better solution. That's a similar method we follow for desktop audits.
--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/33939>
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