mirror of
https://github.com/privacyguides/privacyguides.org.git
synced 2024-10-01 01:35:57 -04:00
c6ee840c9d
* Fix some typos, grammar, etc. on the site Fixes some issues with typos, capitalization, grammar, and et cetera. * Fix typo, grammar, etc. in repository * Update README.md Mention Discourse community earlier, add missing period * Update CONTRIBUTING.md i.e. is used for equivalence or clarification while e.g. is for examples. For instance, we shouldn't say that IMAP is equivalent or an explanation to all open-source software used to access email (e.g. there's POP3, open-source clients to access when there isn't IMAP such as Tutanota, etc.). We also shouldn't call IMAP open-source software since it's a protocol. * Change "socially motivated * Apply suggestions from code review Co-Authored-By: Jonah Aragon <jonah@triplebit.net> * Suggestion from code review with extras * 'Kill switch' to 'Killswitch" * Consistency and minor additions to details - More parallel sentence structures, following <Name> <Verb phrase> for the first sentence of cards. Related to issue #1420. - Make Njalla parallel to the others, and mention Njalla is based in Nevis with VPS in Sweden - Don't use "us" when talking about external services - Orange Website also provides domain registration - Update capitalization and add more hyphens - Mention that TOS;DR evaluations are done by the community and that they also evaluate privacy policies (see https://edit.tosdr.org/about) - "E2EE encryption" is redundant since "E2EE" already has "encryption" in it. Might as well expand it since full term is used later on. - <Name> <Verb phrase> structure for Magic Wormhole - For consistency, don't start Worth Mentioning entries with the name - https://english.stackexchange.com/questions/27707/post-hyphenation-of-split-compound-words - All the other "alert alert-warning" don't repeat the generic name and we also don't say 'a software' * instant-messenger: Remove <em>, more cleanup * voice-video-messenger: Hyphens and cleanup - We don't say "a software" so replace it with something that works * paste-services: Cleanup & change cryptography info As per CryptPad's whitepaper and FAQ: https://cryptpad.fr/faq.html#security-crypto https://blog.cryptpad.fr/images/CryptPad-Whitepaper-v1.0.pdf Fixes #1417. * encryption: "open-source" * Page descriptions and other cleanup
48 lines
2.5 KiB
HTML
48 lines
2.5 KiB
HTML
<h1 id="webrtc" class="anchor"><a href="#webrtc"><i class="fas fa-link anchor-icon"></i></a> WebRTC IP Leak Test - Is your IP address leaking?</h1>
|
|
|
|
<div class="alert alert-danger" role="alert">
|
|
<strong>WebRTC is a new communication protocol that relies on JavaScript that can leak your actual IP address from behind your VPN.</strong>
|
|
</div>
|
|
|
|
<p>While software like NoScript prevents this, it's probably a good idea to block this protocol directly as well, just to be safe.</p>
|
|
|
|
<p>
|
|
<a class="btn btn-warning" target="_blank" rel="noopener noreferrer" href="https://ipleak.net">Test your Browser now</a>
|
|
</p>
|
|
|
|
<h3>How to disable WebRTC in Firefox?</h3>
|
|
|
|
<p>In short: Set "media.peerconnection.enabled" to "false" in "about:config".</p>
|
|
<p><strong>Explained:</strong></p>
|
|
|
|
<ol class="long-string-list">
|
|
<li>Enter "about:config" in the firefox address bar and press enter.</li>
|
|
<li>Press the button "I'll be careful, I promise!"</li>
|
|
<li>Search for "media.peerconnection.enabled"</li>
|
|
<li>Double click the entry, the column "Value" should now be "false"</li>
|
|
<li>Done. Do the WebRTC leak test again.</li>
|
|
</ol>
|
|
|
|
<p>If you want to make sure every single WebRTC-related setting is really disabled change these settings:</p>
|
|
|
|
<ol class="long-string-list">
|
|
<li>media.peerconnection.turn.disable = true</li>
|
|
<li>media.peerconnection.use_document_iceservers = false</li>
|
|
<li>media.peerconnection.video.enabled = false</li>
|
|
<li>media.peerconnection.identity.timeout = 1</li>
|
|
</ol>
|
|
|
|
<p>Now you can be 100% sure WebRTC is disabled.</p>
|
|
|
|
<p>
|
|
<a class="btn btn-primary" target="_blank" rel="noopener noreferrer" href="https://ipleak.net">Test your Browser again</a>
|
|
</p>
|
|
|
|
<h3>How to fix the WebRTC Leak in Google Chrome?</h3>
|
|
|
|
<p>WebRTC cannot be fully disabled in Chrome; however, it is possible to change its routing settings (and prevent leaks) using an extension. Two open-source solutions include <a href="https://chrome.google.com/webstore/detail/webrtc-leak-prevent/eiadekoaikejlgdbkbdfeijglgfdalml">WebRTC Leak Prevent</a> (options may need to be changed depending on the scenario), and <a href="https://chrome.google.com/webstore/detail/ublock-origin/cjpalhdlnbpafiamejdnhcphjbkeiagm">uBlock Origin</a> (select "Prevent WebRTC from leaking local IP addresses" in Settings).</p>
|
|
|
|
<h3>What about other browsers?</h3>
|
|
|
|
<p>Chrome on iOS, Internet Explorer and Safari does not implement WebRTC yet. <a href="#browser"><i class="fas fa-link"></i> But we recommend using Firefox on all devices.</a></p>
|