For firefox, see "Multi Account Containers" and "Temporary Containers". These are extensions, but they just provide UI for inherent functionality. There's also first party isolation standardised privacy feature, same as chrome.
-
-
-
Those features require too much thinking and planning by the user. We need automatic solutions.
-
with the caveat that it depends on the user (I'm far from typical) but yes, I agree. It clearly counts as "should start to investigate doing the same" though.
End of conversation
New conversation -
-
-
I'm not sure how valuable this is (privacy wise) unless you close all the holes (like resumption). In Firefox that's possible with containers or the (experimental) pref for first party isolation. In Tor Browser, it's on by default.
-
And H/2. And socket pools.
-
If you find a bypass in h2, you'll get a bounty from Tor :) Socket pools maybe not though; since they don't use that code.
-
You're saying that H/2 coalescing is disabled, and distinct socket pools per keyed origin are used? Any pointers to the source?
-
They should be! I'll go look tomorrow. :)
-
H2 Coalescing is here: https://searchfox.org/mozilla-central/source/netwerk/protocol/http/Http2Session.cpp#2702 … which flows to https://searchfox.org/mozilla-central/source/netwerk/protocol/http/nsHttpConnectionMgr.cpp#762 …. OriginAttributes always contains a Container ID (if you don't have containers it's 0) and if you have FPI enabled, the first party origin. cc
@mcmanusducksong -
Socket Pools is governed the same way, in https://searchfox.org/mozilla-central/source/netwerk/protocol/http/nsHttpConnectionMgr.cpp#1893 … I did find some scary things about setting the socket reuse: https://searchfox.org/mozilla-central/search?q=symbol:F_%3CT_7d320e23007bb462%3E_4&redirect=false … but comments and discussions indicate this is used safely, only for ICE TCP or local net stuff.
-
So that part isn't very robust and might have some lurking issues but hopefully if present, they're limited. Bypasses welcome =)
End of conversation
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.