We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
This is mostly about UDP traffic (but happens with TCP as well).
We should be able to detect STUN/TURN(s) protocols (and to block requests afterwards).
Detection is possible if we analyze the very first outgoing packet (decrypted in case of stun/turn over tls over tcp).
The text was updated successfully, but these errors were encountered:
Done for TCP in corelibs proxy, but still needed in TCP/IP stack for UDP
Sorry, something went wrong.
core/pull-requests/880 core/pull-requests/884 mac/pull-requests/134
Testing instruction: Turn on stealth mode and webRTC blocking, try to test webrtc leak with something like: https://browserleaks.com/webrtc
sxgunchenko
No branches or pull requests
This is mostly about UDP traffic (but happens with TCP as well).
We should be able to detect STUN/TURN(s) protocols (and to block requests afterwards).
Detection is possible if we analyze the very first outgoing packet (decrypted in case of stun/turn over tls over tcp).
The text was updated successfully, but these errors were encountered: