[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]
Re: [tor-bugs] #1517 [Tor Browser]: Provide JS with reduced time precision
#1517: Provide JS with reduced time precision
-------------------------+-------------------------------------------------
Reporter: | Owner:
mikeperry | Status: needs_review
Type: | Milestone:
enhancement | Version:
Priority: major | Keywords: backport-to-mozilla, tbb-torbutton,
Component: Tor | tbb-fingerprinting-time-highres, ff38-esr,
Browser | TorBrowserTeam201505R, PearlCrescent201505R
Resolution: | Parent ID:
Actual Points: |
Points: 10 |
-------------------------+-------------------------------------------------
Comment (by mcs):
Replying to [comment:25 mikeperry]:
> Here's a patch that should make all JS clock sources and event
timestamps have 100ms resolution, except for keypress events, which should
have 250ms resolution: https://gitweb.torproject.org/user/mikeperry/tor-
browser.git/commit/?h=bug1517. It also clamps internal usage of
DOMHighResTimestamps to 1 microsecond, to avoid internal sidechannels and
other leaks.
Kathy and I reviewed this and the changes look OK. It is hard to say what
might break though.
One question: do you know how the ToMilliseconds() and ToMicroseconds()
calls inside xpcom/ds/TimeStamp.h are exposed to web content? Is
ToSeconds() exposed as well? If so, we should also reduce the resolution
of values returned by ToSeconds().
--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/1517#comment:30>
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