[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]
Re: [tor-bugs] #13543 [Applications/Tor Browser]: HTML5 media support may lead to fingerprinting
#13543: HTML5 media support may lead to fingerprinting
-------------------------------------------------+-------------------------
Reporter: cypherpunks | Owner: tbb-
| team
Type: defect | Status:
| needs_review
Priority: High | Milestone:
Component: Applications/Tor Browser | Version:
Severity: Normal | Resolution:
Keywords: tbb-fingerprinting, ff68-esr, | Actual Points:
TorBrowserTeam201910R, tbb-9.0-must |
Parent ID: | Points:
Reviewer: | Sponsor:
-------------------------------------------------+-------------------------
Changes (by acat):
* status: new => needs_review
* keywords: tbb-fingerprinting, ff68-esr, TorBrowserTeam201910,
tbb-9.0-must => tbb-fingerprinting, ff68-esr, TorBrowserTeam201910R,
tbb-9.0-must
Comment:
I thought a bit more, I don't have a very strong opinion in favor of one
or another, basically because I'm not sure how this API will be used by
websites. But I think it may be better to be conservative and say it's not
power efficient while it actually may be than the opposite. For `smooth`
the same reasoning might apply, but *I think* it's not so common to find
cases where the returned info is `(true, false, false)` (I did not find
those in a couple of home machines, although it may be possible in slow
machines).
Since we have to pick one, I'm voting for `(true, true, false)`:
https://github.com/acatarineu/tor-browser/commit/13543+2.
--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/13543#comment:21>
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