Here's a list of bugs whose patches I cherry-picked or backported from Firefox >=53 without too much difficulty. They are Tor uplift patches or addition first-party isolation work.
1334690 Isolate AlternateService mappings by Origin Attributes1334693 Investigate and isolate SPDY/HTTP2 state by first-party domain when privacy.firstparty.isolate = true1315602 Remove the assertion of FirstPartyDomain should be empty in HTTP redirect1274020 Add a test to show that the DOM Cache is separated by origin attributes1282655 Add a test case to test whether site permissions are universal or isolated for each type of OriginAttribute1305144 Spoof referrer when leaving a .onion domain (Tor 17334)1216893 Add pref to optionally disable SVG (Tor 12827)
Here's the branch with these patches. If this seems reasonable I will merge these with my latest #20680 (moved) branch.
Some patches have substantial conflicts: namely HSTS/HPKP isolation and the network predictor isolation patch. These are going to take further work:
1290529 clear HSTS and HPKP for subdomains as well when bug 1115712 is fixed1323644 Isolate the HSTS and HPKP cache by first party domain.1336867 Remove unsafeProcessHeader and isSecureHost in nsISiteSecurityService1115712 make DataStorage for HPKP and HSTS enumerable via xpcom1317927 Media caching needs to use origin attributes1312954 Making the network predictor obey originAttributes and updating SpeculativeConnect() to SpeculativeConnect2().
Trac: Keywords: N/Adeleted, TorBrowserTeam2017R added Status: new to needs_review
I have not looked closely at the patches but for now we don't need
1334690 Isolate AlternateService mappings by Origin Attributes1334693 Investigate and isolate SPDY/HTTP2 state by first-party domain when privacy.firstparty.isolate = true
.
We have H2 and SPDY still disabled and will have to audit it first for other issues. We can then apply the backported patches (if we get to that before esr59).
As to the patches with substantial conflicts: we would want to have those. (Or write our own).
As to the patches with substantial conflicts: we would want to have those. (Or write our own).
Although the network predictor is currently disabled. Thus here we should weigh the benefits with the complexity the new code introduces (we have #16633 (moved) for that fwiw and we might want to look at #16625 (moved) again as well. Especially: "The seer does not record any data, nor does it take any action, when in private browsing mode." seems worth to contemplate as we are in permanent private browsing mode.
I have now backported the HSTS/HPKP patches. It required several other patches to be backported as well.
So here is a branch based on 20680+8 that contains all previously backported patches for this ticket plus HSTS/HPKP stuff.
https://github.com/arthuredelstein/tor-browser/commits/21340+4
tbb-nightly:
SVG is visible with svg.disabled=true (also svg.in-content.enabled=true exists on High Sec)
Thanks. That's #21885 (moved) now.
You're welcome (:
Also downloading of zip file stalls reliably at 0 bytes with
{{{
[04-07 10:07:18] Torbutton INFO: External app requested
http channel Listener OnDataAvailable contract violation
}}}
Yes, I had seem something like that before but did not get to file a ticket yet. It is #21886 (moved) now (which contains a workaround as well), thanks.
tbb-nightly:
SVG is visible with svg.disabled=true (also svg.in-content.enabled=true exists on High Sec)
Thanks. That's #21885 (moved) now.
You're welcome (:
Also downloading of zip file stalls reliably at 0 bytes with
{{{
[04-07 10:07:18] Torbutton INFO: External app requested
http channel Listener OnDataAvailable contract violation
}}}
Yes, I had seem something like that before but did not get to file a ticket yet. It is #21886 (moved) now (which contains a workaround as well), thanks.
I think it's the same issue as in #21766 (moved), but with e10s off. Your workaround is the same as mine (:
Also enabling plug-ins works only once: enable, press "no" to undo, enable again, and then there is no message box again, and no way to disable plug-ins as "disable plugins" button is missed in esr52.
These include the HSTS/HPKP-related patches, as well as these:
1315602 Remove the assertion of FirstPartyDomain should be empty in HTTP redirect1274020 Add a test to show that the DOM Cache is separated by origin attributes1282655 Add a test case to test whether site permissions are universal or isolated for each type of OriginAttribute1305144 Spoof referrer when leaving a .onion domain (Tor 17334)
I should also mention I attempted to rebase the implementation patch from https://bugzilla.mozilla.org/show_bug.cgi?id=1342178 but found that it didn't seem to fix the problem described on that ticket, presumably because my rebasing isn't quite right. It's rather complex, so I'm leaving it out for now.
These include the HSTS/HPKP-related patches, as well as these:
{{{
1315602 Remove the assertion of FirstPartyDomain should be empty in HTTP redirect
1274020 Add a test to show that the DOM Cache is separated by origin attributes
1282655 Add a test case to test whether site permissions are universal or isolated for each type of OriginAttribute
1305144 Spoof referrer when leaving a .onion domain (Tor 17334)
}}}
I think I don't get to those anymore for 7.0a3. :( We should consider them for the next alpha.
These include the HSTS/HPKP-related patches, as well as these:
I put the HSTS/HPKP patch review into #17965 (moved). Right now I am inclined to postpone inclusion and have those patches the first alpha of the 7.5 series as this is quite complex and might need more testing. Not sure about backporting to the 7.0 series in that case.
> 1315602 Remove the assertion of FirstPartyDomain should be empty in HTTP redirect
commit efd86213b996d351757498968481962eb610c06c
> 1274020 Add a test to show that the DOM Cache is separated by origin attributes
commit 3da33fc90ce348fbc594d5aa45e85d8a4f08e539
> 1282655 Add a test case to test whether site permissions are universal or isolated for each type of OriginAttribute
commit 59cba8d0681caf53c46cd3718e34c9a49f9c5921
> 1305144 Spoof referrer when leaving a .onion domain (Tor 17334)
That got already included and is commit 4317d7a834b0abf95ba6afdb18902758c691da49. All commits are on tor-browser-52.1.0esr-7.0-2.