Join GitHub today
GitHub is home to over 50 million developers working together to host and review code, manage projects, and build software together.
Sign upg.3gl.net RPC tracking & refresh call fix #17
Labels
Comments
|
PR #18 |
|
Merged |
|
Re-opening - We need to expand this to cover more domains, or apply as a global filter. Investigating. This is a bad one. |
|
This is tied to IL - going to try some fixes for this in brave, and in this repo. |
|
Does brave browser team stopped acting against IL.....no commit since 4months on this IL crap? |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Observed RPC tracking bypassing Shields on boston.com and sfgate.com (likely Google gRPC)
Strong suspicion this is google, or from a google partner. Definite references to hawklogserver domains, but searches result in either pen testing for windows or vague google references. The absence of search results is suspect given the data passed, and behavior of the requests.
I've tested the filter rule and am able to confirm successful blocking, and no noticeable issues with Google access.
Two requests take place, which then refresh. The second request passes ad, cookie and location data from the user, which appears to pass device data as well.
This is what we're blocking:
Request URL:
https://g.3gl.net/jp/100/v2/CResponse:
Request URL:
Response: