Tor Browser in its default mode (i.e. with JavaScript allowed) freezes when loading http://zeit.de. This happens every time when requesting https://www.facebook.com/tr/.
My console output stops always with
[05-23 16:59:52] Torbutton INFO: tor SOCKS: https://www.facebook.com/tr/ via zeit.de:a137cc9014c3589a23fe6c5d354a4d7d
After a bit of debugging it turns out that vanilla Firefox 52 versions are affected as well but only if NoScript is installed. This happens with NoScript 5.0.4 at least.
To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Child items ...
Show closed items
Linked items 0
Link issues together to show that they're related.
Learn more.
Giorgio: let me know if you have issues with reproducing this. I have saved a local copy of the website and could send it to you as I can see the issue with that copy as well.
Trac: Description: Tor Browser in its default mode (i.e. with JavaScript allowed) freezes when loading zeit.de. This happens every time when loading https://www.facebook.com/tr/.
My console output stops always with
[05-23 16:59:52] Torbutton INFO: tor SOCKS: https://www.facebook.com/tr/ via zeit.de:a137cc9014c3589a23fe6c5d354a4d7d
After a bit of debugging it turns out that vanilla Firefox 52 versions are affected as well but only if NoScript is installed. This happens with NoScript 5.0.4 at least.
to
Tor Browser in its default mode (i.e. with JavaScript allowed) freezes when loading http://zeit.de. This happens every time when loading https://www.facebook.com/tr/.
My console output stops always with
[05-23 16:59:52] Torbutton INFO: tor SOCKS: https://www.facebook.com/tr/ via zeit.de:a137cc9014c3589a23fe6c5d354a4d7d
After a bit of debugging it turns out that vanilla Firefox 52 versions are affected as well but only if NoScript is installed. This happens with NoScript 5.0.4 at least.
Trac: Description: Tor Browser in its default mode (i.e. with JavaScript allowed) freezes when loading http://zeit.de. This happens every time when loading https://www.facebook.com/tr/.
My console output stops always with
[05-23 16:59:52] Torbutton INFO: tor SOCKS: https://www.facebook.com/tr/ via zeit.de:a137cc9014c3589a23fe6c5d354a4d7d
After a bit of debugging it turns out that vanilla Firefox 52 versions are affected as well but only if NoScript is installed. This happens with NoScript 5.0.4 at least.
to
Tor Browser in its default mode (i.e. with JavaScript allowed) freezes when loading http://zeit.de. This happens every time when requesting https://www.facebook.com/tr/.
My console output stops always with
[05-23 16:59:52] Torbutton INFO: tor SOCKS: https://www.facebook.com/tr/ via zeit.de:a137cc9014c3589a23fe6c5d354a4d7d
After a bit of debugging it turns out that vanilla Firefox 52 versions are affected as well but only if NoScript is installed. This happens with NoScript 5.0.4 at least.
ABE complains in that case. It seems it does not know "Allow". But replacing that with "Accept" makes it happy. Let me know if that's not the right thing. However, after restarting and with that rule in place I still get the hangs.
Replying But replacing that with "Accept" makes it happy.
However, after restarting and with that rule in place I still get the hangs.
Yes, it's "Accept", my bad.
It doesn't seem **caused **by the load (it's just a 1 pixel GIF), but maybe just correlated and, I suspect, caused by a script checking for something that's not there in a loop.
Going on with the investigation and looking for work-arounds...
It gets loaded several times with GET requests, but at a certain point a POST request containing two big JSON parameter is sent, and this apparently hangs the XSS filter (which is triggered BEFORE ABE, hence the futility of my previous proposed work around).
While I try to understand what actually happens in the guts of the filter, a new work around which WFM is adding the following line to NoScript Options>Advanced>XSS exceptions box (about:config -> noscript.filterXExceptions):
It gets loaded several times with GET requests, but at a certain point a POST request containing two big JSON parameter is sent, and this apparently hangs the XSS filter (which is triggered BEFORE ABE, hence the futility of my previous proposed work around).
Woah. Thanks for looking into it. The workaround does the job for me as well.
While I try to understand what actually happens in the guts of the filter, a new work around which WFM is adding the following line to NoScript Options>Advanced>XSS exceptions box (about:config -> noscript.filterXExceptions):
ma1: Do you have an ETA for a new NoScript version with a fix for this problem? I am a bit reluctant to add that exception to the list for Tor Browser. But we are currently preparing Tor Browser 7.0, so having this issue solved some time next week or early in the week thereafter would rock.
After thinking a while about how to mitigate that problem in Tor Browser while we are waiting for a new NoScript release it seems to me we don't want to just whitelist that particular tracker. The risk is that a week after release a different one hits the same bug and we start playing whack-a-mole. I think we should disable the XSS protection for now until it can't be used as a DoS tool anymore.