[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]
Re: [tor-bugs] #13035 [Tor Browser]: Make sure our cache isolation works with cache2
#13035: Make sure our cache isolation works with cache2
-------------------------+-------------------------------------------------
Reporter: gk | Owner: mcs
Type: task | Status: assigned
Priority: major | Milestone:
Component: Tor | Version:
Browser | Keywords: ff38-esr, tbb-linkability, tbb-
Resolution: | fingerprinting
Actual Points: | Parent ID:
Points: |
-------------------------+-------------------------------------------------
Changes (by mcs):
* cc: arthuredelstein (added)
Comment:
Our initial conclusion is that the we are in good shape: isolation is
being done correctly. This conclusion is mainly based on reviewing the
ESR 38 code and the patch that Arthur rebased, along with some time spent
in gdb with cache2 logging enabled.
With respect to https://bugzilla.mozilla.org/show_bug.cgi?id=962334, based
on code inspection the Mozilla people are correct: the cache entries are
immediately (synchronously) removed from hash tables so the old cache
items will not be returned to callers.
Kathy and I want to do a little more testing before we close this ticket
though.
Does anyone know if the netwerk/test/browser/browser_cacheFirstParty.js
tests are working when run on Arthur's ESR 38 branch? Kathy and I have not
tried to run those yet.
--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/13035#comment:4>
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