Skip to content
New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

$stealth exceptions do not work on the TCP stack level where we block STUN/TURN #1737

Closed
2 of 4 tasks
nightznero opened this issue Mar 21, 2023 · 2 comments
Closed
2 of 4 tasks

Comments

@nightznero
Copy link

nightznero commented Mar 21, 2023

Please answer the following questions for yourself before submitting an issue.

  • I am running the latest version
  • I checked the documentation and found no answer
  • I checked to make sure that this issue has not already been filed

AdGuard version

3.6.54

Environment

- OS: A13
- Firmware: Newest

Root access

  • Yes, I have it.

What filters do you have enabled?

No response

What Stealth Mode options do you have enabled?

Hide your search queries, Send Do-Not-Track signals, Strip URLs of tracking parameters, Self-destruction of third-party cookies, Disable cache for third-party requests, Block the third-party Authorization header, Disable WebRTC, Block Push API, Block Location API, Block Flash, Disable Windows Telemetry, Turn off Advertising ID, Hide your Referrer from third-parties, Hide your User Agent, Hide your IP address, Remove X-client-Data header from HTTP request, Protect from DPI

Issue Details

.

Expected Behavior

Simple whitelisting

Actual Behavior

No matter what rule or what modifier I use, SM still blocks IPs,same goes for e.x Google Play Store if I want unblock some of IPs but results are the same,no matter what rule is used...nothing changes. Because of that I cannot safety watch some streams and have to disable ADG,what is pointless...cause I m ising 24/7 ADG and can't live without it
Also worthy mentioning, modifiers like 3p-cookie etc doesn't work. SM can be only fully disabled,not particularly and its sad cuz this could fix also my issue :)

Screenshots

What is blocked
Screenshot_20230321_223326_AdGuard
User Rule
Screenshot_20230321_223400_AdGuard
DNS Rule
Screenshot_20230321_223420_AdGuard

Additional Information

Would be nice to fix it in maybe new rewritten ADG cuz in old ADG this issue exists since SM has been added.

@maxikuzmin maxikuzmin transferred this issue from AdguardTeam/AdguardForAndroid Mar 22, 2023
@adguard-bot adguard-bot changed the title Stealth Mode vs Whitelisting $stealth exceptions do not work on the TCP stack level where we block STUN/TURN Aug 4, 2023
@ameshkov
Copy link
Member

ameshkov commented Aug 4, 2023

There could be two solutions to this.

  1. Extend CL to support $stealth on the TCP stack level.
  2. Remove the option to block WebRTC as it may not be useful anymore. As I understand, webRTC does not leak IP addresses in the modern browsers. This point needs to be verified.

@nightznero
Copy link
Author

Also noticed other weird working SM feature. First-Party Cookies

# for free to join this conversation on GitHub. Already have an account? # to comment
Projects
None yet
Development

No branches or pull requests

4 participants