prox-config-sidki_2019-01-26b1
|
Sep. 16, 2019, 04:33 PM
(This post was last modified: Sep. 16, 2019 04:35 PM by JJoe.)
Post: #17
|
|||
|
|||
RE: prox-config-sidki_2019-01-26b1
(Sep. 15, 2019 02:42 AM)thypentacle Wrote: For issue 2 I think I fixed that one on my end by not using Opera. I use the new Opera portable. (Sep. 15, 2019 02:42 AM)thypentacle Wrote: For issue 3 here's a few that fail loading... Ahh... Filtering will break web sites. The user is expected to add 'Exceptions' to 'Exceptions-U.ptxt' to regain desired behavior. However, I'll claim discordapp and teams.microsoft.com. Depending on which cfg you are using, 'Exceptions-U.ptxt' needs at least: Code: ##community.quirky.com/login Discordapp's Content-Security-Policy header uses nonce. Code: default-src https://local.ptron:8443 'unsafe-inline' 'self'; 'Nonce' causes the browser to ignore our 'unsafe-inline' addition and our inline scripts for discordapp.com/channels/@me. The simple choice is to bypass the affected pages or add Exceptions for the broken routines. Another is to remove "nonce' from the header. Warning: This would also allow malicious scripts without the nonce attribute to run. Code: [HTTP headers] The better (for our point of view) but more time consuming choice would be to capture the nonce and add it to our rewritten scripts. discordapp is also using the integrity attribute. Code: <script src="/assets/dea071166a0cf8791a1e.js" integrity="sha256-0kdB3V4HCTqbit21e3K2rY7ypJiNdjmjyQ9MFnPJHCI= sha512-EtY9vjf3AHCuuRqOurhkNITyJtCXmfgFQmOCD4w/LbtgvstqFufIiFfTetU24nhw+n1CD//myNXaNa59lT9EQg=="> The browser will reject the script if its hash isn't the integrity attribute's value. A filtered script's hash will not match. The simple choice is to bypass the affected resources. ![]() Warning: This would also allow malicious files to run. Code: [Patterns] more to come... |
|||
« Next Oldest | Next Newest »
|