Configure (Private) (Obfuscated) Tor Bridges

Whonix ®

Download

Windows Linux Mac VirtualBox KVM Qubes USB ISO (coming soon) More options Source Code

About

Overview Features Whonix vs VPNs Why Open Source? Project Activities Contributors Mission & Vision

Docs

Documentation FAQ Troubleshooting

Community

Forums Contribute

Support

Self Support First Policy Search Engines, Docs and AI Support (Limited) Reporting Bugs Contact (Restricted)

Tools Upload file Special pages Recent changes Print Version Page meta What links here Related changes Page information

Page Read Edit History Move Protection Unwatch Watch Delete Purge

User Preferences Watchlist Contributions Logout Create account Login

Donate

• Network Obstacle
• Configure (Private) (Obfuscated) Tor Bridges
• Hide Tor use from the internet service provider (ISP)

Censorship Circumvention. Get around network bans. Using Whonix with (private) (obfuscated) bridges. Useful in case your Internet Service Provider (ISP) bans or throttles connections to the Tor public network.

Bridges Description and User Groups

Introduction

If a website cannot be reached over Tor, this does not necessarily relate to network level censorship that requires a bridge to be configured; it may relate to blacklisting of all Tor exit IP addresses by the server. In that case, see Geo-blocking for circumventing censorship by destination servers.

When Tor is used with Whonix in the default configuration, anybody observing the properties of its application protocol can discover its presence. Potential observers include the Internet Service Provider (ISP), advanced adversaries, censorship enforcement bodies and other interested parties.

Tor bridges ("Tor bridge relays") are alternative entry points to the Tor network, acting as substitutes to regular Tor guards rather than an additional hop to the 3 hop journey. Not all bridges are obtainable publicly. Using a bridge makes it harder, but not impossible, for the ISP to determine if a user is connecting to Tor.

Intended User Groups

Tor non-functionality is often related to local configuration problems rather than ISP or state-level censorship.

For the majority of Whonix users, connecting to Tor with the default configuration is appropriate and will work successfully. The minority of users requiring a bridge normally fall into three categories:

• Tor is blocked, and some way - any way - to reach the network has to be found. The adversary is not very dangerous, but very annoying.
• Tor may or may not be blocked, but the users are trying to hide the fact they're using Tor. The adversary may be extremely dangerous.
• Other bridge users: Testing whether the bridge works (automated or manual), probing, people using bridges without their knowledge because they came pre-configured in their bundle.

The first group of users is only concerned with circumventing Tor censorship that is based on IP address or fingerprinting of protocols. Circumvention is necessary because Whonix would otherwise be rendered useless for most activities except working offline on documents and so on, since all Internet traffic is routed through Tor by default. This group is not worried about hiding the use of Tor and will need to use bridges or possibly other circumvention tools.

The second user group is unable to safely start Whonix in the default configuration due to Tor being considered dangerous or suspicious in their locality. In this case private bridges should be utilized instead of public obfuscated bridges, as this makes it harder (not impossible) to detect Tor.

Note that the meek_azure pluggable transport may be necessary to deal with highly aggressive ISP censorship or national firewalls, like those found in China and the Middle East.

The third group is only concerned with testing bridge connections.

Before Configuring a Bridge

Warning: Bridges are important tools that work in many cases but they are not an absolute protection against the technical progress an adversary might make in identifying Tor users. Using bridges might be advisable to prevent identification as a Tor user, but the Tor Project's bridges documentation is primarily focused on censorship circumvention, that is, overcoming attempts by ISPs or government to block Tor use.

Users falling into one of the three groups described above should consider using Tor bridges. Before taking this step, please review The Tor Project's dedicated bridges page to better understand their design and operation. It is also recommended to review how Obfsproxy works, since it is the most commonly used application for connecting bridges.

Always remember that bridges are not bullet-proof. The following is a reminder about bridge versus non-bridge anonymity:

Quote Roger Dingledine, cofounder of Tor:

[...] Bridges are less reliable and tend to have lower performance than other entry points. If you live in a uncensored area, they are not necessarily more secure than entry guards. [...]

Quote question:

If that is true, that also means, that bridge users are sufficiently more vulnerable to attacks, which are circumvented by entry guards?

Quote Roger Dingledine, cofounder of Tor:

[...] They're probably more vulnerable, but I don't know if I'd say "sufficiently". [...]

If a user is only concerned with connectivity (getting Whonix connected) and local ISPs do not usually hinder connections to the public Tor network, then something simpler than Bridges can be tried; see: Better Connectivity without Real Censorship Circumvention.

Additional Information and Recommendations

For safety reasons, the first run of Whonix will not automatically connect to the public Tor network. Instead, user networking decisions are guided by Anon Connection Wizard which automatically starts.

When deciding on the type of bridge to configure, it is recommended to:

• Prefer obfuscated bridges, since they are harder to identify than other bridges.
• Use less well-known bridges, since it is safer.
• Avoid using a meek provider that also runs DNS core servers, like Google's (now defunct) bridge.
• Note that domain fronting has been pulled by Google and Amazon, limiting the meek pluggable transport options to meek_azure only in Anon Connection Wizard.
• For greater safety, use a private obfuscated bridge run by a trusted friend or organization in a different country. In this case "private" means that the bridge is configured with the option PublishServerDescriptor 0.

Please note that it has been assessed as difficult beyond practicality to Hide Tor use from the Internet Service Provider with proxies, bridges, VPNs or SSH tunnels.

Finding a Bridge and Choosing the Right Protocol

In order to use bridges, the address of at least one bridge must be known in advance. It is preferable to have a private obfuscated bridge because the alternative -- public obfuscated bridges -- are more likely to be censored, since they are publicly listed. The Tor Project distributes public bridge addresses in several ways, including from their website and via email. The easiest way to find a list of public bridges is from The Tor Project Bridge Database.

In early 2017, The Tor Project advice regarding recommended bridges changed:

... in Tor Browser to obfs4, given that we now have several high capacity obfs4 bridges and obfs4 is more likely to work in more regions than obfs3."

As time has gone on, more obfs4 bridge operators have come online, and obfs4 is now routinely recommended by Tor developers over obfs3, because the former:

... should be able to defend more effectively against active probing.

As a consequence, obfs3 bridges have been deprecated as a configurable pluggable transport option in Tor Browser. Also see: obfs4 Transport Evaluation.

The Tor Project provides a database of public obfs4 bridges. A more exhaustive list of public obfuscated bridges is available at The Tor Project Bridge Database. obfs and obfs2 bridges are no longer available since they:

... are now deprecated and were replaced by obfs3 . . . and obfs4.

Do not select the "IPv6 compatible" check box when sourcing bridges from the database, as they cannot be used in Whonix yet.

How to Use Bridges in Whonix

It is possible to configure obfs4 and meek_azure (meek lite) bridges.

Two options. Choose either option A) or B).

• A) Anon Connection Wizard GUI application - recommended for most users. See instructions below. Or,
• B) Manual Bridge Configuration - advanced users.

1. Start Anon Connection Wizard.

If you are using Qubes-Whonix^™, complete the following steps.

Qubes App Launcher (blue/grey "Q") → Whonix-Gateway™ ProxyVM (commonly named sys-whonix) → Anon Connection Wizard

If you are using a graphical Whonix-Gateway, complete the following steps.

Start Menu → Applications → System → Anon Connection Wizard

If you are using a terminal emulator (such as for example xfce4-terminal) on Whonix-Gateway, type.

lxsudo anon-connection-wizard

If you are using a CLI Whonix-Gateway, see footnote.

2. Use the Bridge Configuration Page

Option 1: Anon Connection Wizard has some built-in bridges. To use them, complete the following steps.

Select "Configure" in the beginning page → Select "I need Tor bridges to bypass the Tor censorship" → Select "Connect with provided bridges" → Select a transport type that is suitable.

Tip: If it is unknown which transport type is the most suitable or likely to work, then simply try them all until one is functional. It is recommended to first start with obfs4, and then only try meek if it does not work.

Option 2: If none of the default bridges work, the user can try to obtain a set of bridges manually. See Finding a Bridge and Choosing the Right Protocol. After obtaining a set of Tor bridges, complete the following step.

Select "Configure" in the beginning page → Select "I need Tor bridges to bypass the Tor censorship" → Select "Enter custom bridges" → Copy and paste the set of bridges to that input box(one bridge per line)

Experimental Bridges

Snowflake

Introduction of Snowflake

Snowflake is:

...a pluggable transport that proxies traffic through temporary proxies using ​WebRTC, a peer-to-peer protocol with built-in NAT punching. It aims to work kind of like flash proxy, but without flash proxy's problems with NAT.

Setup Snowflake

On Whonix-Gateway.

1. Edit the Tor configuration file.

Open file /usr/local/etc/torrc.d/50_user.conf in a text editor of your choice with sudoedit.

If you are using Qubes-Whonix^™, complete the following steps.

Qubes App Launcher (blue/grey "Q") → Whonix-Gateway™ ProxyVM (commonly named sys-whonix) → Tor User Config (Torrc)

If you are using a graphical Whonix-Gateway, complete the following steps.

Start Menu → Applications → Settings → /usr/local/etc/torrc.d/50_user.conf

If you are using a terminal-only Whonix-Gateway, complete the following steps. sudoedit /usr/local/etc/torrc.d/50_user.conf

2. Paste the following setting.

UseBridges 1 ClientTransportPlugin snowflake exec /usr/bin/snowflake-client Bridge snowflake 192.0.2.3:80 2B280B23E1107BB62ABFC40DDCC8824814F80A72 fingerprint=2B280B23E1107BB62ABFC40DDCC8824814F80A72 url=https://1098762253.rsc.cdn77.org/ fronts=www.cdn77.com,www.phpmyadmin.net ice=stun:stun.l.google.com:19302,stun:stun.antisip.com:3478,stun:stun.bluesip.net:3478,stun:stun.dus.net:3478,stun:stun.epygi.com:3478,stun:stun.sonetel.com:3478,stun:stun.uls.co.za:3478,stun:stun.voipgate.com:3478,stun:stun.voys.nl:3478 utls-imitate=hellorandomizedalpn Bridge snowflake 192.0.2.4:80 8838024498816A039FCBBAB14E6F40A0843051FA fingerprint=8838024498816A039FCBBAB14E6F40A0843051FA url=https://1098762253.rsc.cdn77.org/ fronts=www.cdn77.com,www.phpmyadmin.net ice=stun:stun.l.google.com:19302,stun:stun.antisip.com:3478,stun:stun.bluesip.net:3478,stun:stun.dus.net:3478,stun:stun.epygi.com:3478,stun:stun.sonetel.net:3478,stun:stun.uls.co.za:3478,stun:stun.voipgate.com:3478,stun:stun.voys.nl:3478 utls-imitate=hellorandomizedalpn

3. DNS resolving in Whonix-Gateway.

Snowflake-client needs to resolve the -front domain to an IP address, in order to connect to the server; however, this DNS resolving will fail with the default Whonix gateway DNS configuration.

Clearnet Whonix-Gateway System DNS.

1. Apply the following changes to Whonix-Gateway^™.

Open file /etc/resolv.conf.whonix in an editor with root rights.

Non-Qubes-Whonix^™

This box uses sudoedit for better security.

sudoedit /etc/resolv.conf.whonix

Qubes-Whonix^™

NOTES:

• When using Qubes-Whonix, this needs to be done inside the Template.

sudoedit /etc/resolv.conf.whonix

• After applying this change, shutdown the Template.
• All App Qubes based on the Template need to be restarted if they were already running.
• This is a general procedure required for Qubes and unspecific to Qubes-Whonix^™.

Others and Alternatives

• This is just an example. Other tools could achieve the same goal.
• If this example does not work for you or if you are not using Whonix, please refer to this link.

sudoedit /etc/resolv.conf.whonix

2. Uncomment the line #nameserver 10.0.2.3.

Remove the hash ("#") before nameserver. This means you should change #nameserver 10.0.2.3 to nameserver 10.0.2.3.

3. Follow platform-specific steps:

• Non-Qubes-Whonix: Done.
• Qubes-Whonix^™: This should typically work. If not, refer to the footnote.

4. Done.

The configuration for Whonix-Gateway System DNS is complete.

5. Note for wiki editors.

Once Whonix 17.2.2.6 or above is released, anon-dns can be used and then the DNS enabling part can be simplified.

4. Restart Tor.

Select your platform.

Non-Qubes-Whonix

Start Menu → Applications → Settings → Restart Tor

Qubes-Whonix

Qubes App Launcher (blue/grey "Q") → Whonix-Gateway™ ProxyVM (commonly named 'sys-whonix') → Restart Tor

Terminal

Restart Tor.

sudo service tor@default restart

Check Tor's daemon status.

sudo service tor@default status

It should include a a message saying.

Active: active (running) since ...

In case of issues, try the following debugging steps.

Check Tor's config.

anon-verify

The output should be similar to the following.

/===================================================================\
|                      Report Summary                               |
\===================================================================/
No error detected in your Tor configuration.

5. Done.

The procedure is complete.

Snowflake forum discussion:

• https://forums.whonix.org/t/replacing-meek-snowflake/5190
• https://forums.whonix.org/t/use-snowflake-in-whonix-to-bypass-tor-censorship/13441

Optional Snowflake Configuration

Use AMP cache rendezvous for Snowflake

Optional.

wkrp stated in a post:

by default in Tor Browser, Snowflake does rendezvous using a domain-fronted HTTPS request. Now there is an alternative (backup) to domain fronting rendezvous: AMP cache rendezvous. If one rendezvous method is blocked, there is a chance the other will work.

Replace the second line in /usr/local/etc/torrc.d/50_user.conf with:

Undocumented.

Debugging Snowflake

Snowflake Usage Verification

Optional.

Make sure Tor is using snowflake.

To check if Tor is indeed using snowflake, we use nyx or onioncircuits. We are connecting to the Tor network through snowflake if:

• In nyx, the guard node is a local address, like 192.168.0.1;
• or in onioncircuits, the guard node IP is Unknown.

Snowflake log analysis

Optional.

1. Enable and view Snowflake log.

We can enable the snowflake log for debugging purposes by appending -log snowflake.log -log-to-state-dir to the ClientTransportPlugin snowflake... line in /usr/local/etc/torrc.d/50_user.conf.

2. We can view the snowflake log with:

sudo less /var/lib/tor/pt_state/snowflake.log

3. Tor data directory.

Note that we can always find the Tor DataDirectory with the following command:

anon-verify -v

DataDirectory /var/lib/tor

Unsupported Pluggable Transport

WebTunnel

WebTunnel is an undocumented pluggable transport.

Rationale for Unsupported Bridges

Why are some pluggable transports unsupported? This is a technical explanation. Users are free to skip it.

The situation is similar to how it was for Snowflake for a long time. WebTunnel is unavailable from packages.debian.org. It is therefore difficult, maintenance time intensive for Whonix to install WebTunnel in Whonix by default. Related: Default Application Policy.

Without volunteer development contributions to Whonix this will probably take a few years, if it ever happens.

References:

• https://forums.whonix.org/t/adding-webtunel-bridges-to-whonix/19675/1
• https://blog.torproject.org/introducing-webtunnel-evading-censorship-by-hiding-in-plain-sight/
• https://community.torproject.org/relay/setup/webtunnel/

Warning: Bridged Networking

Do not change VirtualBox settings on the host operating system for Whonix-Gateway's first or second network interface to a bridged network! This is unsupported, untested and should not be necessary. This is elaborated in wiki chapter Whonix-Gateway Security, Warning: Bridged Networking.

Troubleshooting

Check Tor Network Connection is Using a Tor Bridge

Concerned bridge users can complete a simple check.

1. Open Nyx as follows.

If you are using Qubes-Whonix^™, complete the following steps.

Qubes App Launcher (blue/grey "Q") → Whonix-Gateway™ ProxyVM (commonly named sys-whonix) → Nyx - Status Monitor for Tor

If you are using a graphical Whonix-Gateway, complete the following steps.

Start Menu → Applications → System → Nyx - Status Monitor for Tor

If you are using a terminal Whonix-Gateway, type.

nyx

2. Use the right arrow button to navigate to page 2 of 5 in Nyx.

3. If a bridge is in use, the circuit information will be similar to this.

192.168.0.1 UNKNOWN 1 / Guard

4. If a bridge is not in use, the circuit information will be similar to this.

IP Nickname 1 / Guard

The IP is the real IP (not 192.168.0.1) of the Guard, and the Nickname is the name of that Guard relay.

5. Exit Nyx by pressing the following.

q
q

Connection Issues

After configuration, connection problems can relate to firewall settings that block outgoing connections to the ports provided by the bridge. To check the port the bridge is using, see the following example.

bridge 109.195.132.77:22321

In this example, the IP address is 109.195.132.77, while the the port is 22321.

Try using a (private) (obfuscated) bridge that uses port 80 or 443, as these ports are mostly used for web browsing and therefore usually unblocked.

Trying Packet Size and Timing Obfuscation for obfs4

If a provided obfs4 bridge does not work, the user can try enabling packet size and timing obfuscation by changing the iat-mode value in each last line to either 1 or 2.

Better Connectivity without Real Censorship Circumvention

If a user is only concerned with connectivity (getting Whonix connected) and there is no need to attempt to Hide Tor use from the Internet Service Provider and/or local ISPs do not usually hinder connections to the public Tor network, then something simpler than Bridges can be tried.

The following setting only establishes Tor connections to public Tor network relays that listen on ports 80 and 443.

1. Edit the Tor configuration file.

Open file /usr/local/etc/torrc.d/50_user.conf in a text editor of your choice with sudoedit.

If you are using Qubes-Whonix^™, complete the following steps.

Qubes App Launcher (blue/grey "Q") → Whonix-Gateway™ ProxyVM (commonly named sys-whonix) → Tor User Config (Torrc)

If you are using a graphical Whonix-Gateway, complete the following steps.

Start Menu → Applications → Settings → /usr/local/etc/torrc.d/50_user.conf

If you are using a terminal-only Whonix-Gateway, complete the following steps. sudoedit /usr/local/etc/torrc.d/50_user.conf

2. Add the following setting.

FascistFirewall 1

3. Save the file and have the changes take effect.

Reload Tor.

After changing Tor configuration, Tor must be reloaded for changes to take effect.

Note: If Tor does not connect after completing all these steps, then a user mistake is the most likely explanation. Recheck /usr/local/etc/torrc.d/50_user.conf and repeat the steps outlined in the sections above. If Tor then connects successfully, all the necessary changes have been made.

If you are using Qubes-Whonix^™, complete the following steps.

Qubes App Launcher (blue/grey "Q") → Whonix-Gateway™ ProxyVM (commonly named 'sys-whonix') → Reload Tor

If you are using a graphical Whonix-Gateway, complete the following steps.

Start Menu → Applications → Settings → Reload Tor

If you are using a terminal-only Whonix-Gateway, click HERE for instructions.

Complete the following steps.

Reload Tor.

sudo service tor@default reload

Check Tor's daemon status.

sudo service tor@default status

It should include a a message saying.

Active: active (running) since ...

In case of issues, try the following debugging steps.

Check Tor's config.

sudo -u debian-tor tor --verify-config

The output should be similar to the following.

Sep 17 17:40:41.416 [notice] Read configuration file "/usr/local/etc/torrc.d/50_user.conf".
Configuration was valid

The procedure is complete.

Missing ClientTransportPlugin Line

When a user has configured the following.

bridge obfs4 ...:... ... cert=... iat-mode=0

But forgot to add the corresponding line.

ClientTransportPlugin obfs4 exec /usr/bin/obfs4proxy

Then warnings will only be shown in logs.

[warn] We were supposed to connect to bridge '...:...' using pluggable transport 'obfs4', but we can't find a pluggable transport proxy supporting 'obfs4'. This can happen if you haven't provided a ClientTransportPlugin line, or if your pluggable transport proxy stopped running.

Missing ClientTransportPlugin Executable

[warn] Could not launch managed proxy executable at '/usr/bin/obfs4proxy' ('No such file or directory').

Deprecated Tor Pluggable Transports

Scramblesuit

scramblesuit: Unrecommended (see footnote). Use the provided obfs4 instructions instead.

Flashproxy

flashproxy: Unrecommended (see footnote). Use the provided obfs4 instructions instead.

See Also

• Lantern: An alternative censorship circumvention tool documented for Qubes-Whonix^™ only.
• Unfinished: Censorship Circumvention Tools other than bridges.

Appendix

Hosting Bridges

While most of this chapter is dedicated to bridge use, this section clarifies a few concepts about Tor Bridge hosting, although detailed how-to instructions are not provided. To help others you must reside in a country that does not censor Tor and have a reasonably fast connection. The VM or host in use should have port forwarding enabled to allow direct connections because all bridge server types require this, including Snowflake.

Volunteer Snowflake instances run proxies to the bridge and are not bridges themselves. These proxies can be run behind a NAT because clients use the built-in NAT punching properties of WebRTC to connect. The proxies then open a WebSocket connection to the Snowflake bridge and relay data between the WebRTC connection with the client and the bridge. The Snowflake bridges cannot run behind a NAT and are similar to all other existing pluggable transports in this regard.

Using bridge users' traffic to mask your own onion service traffic is difficult to do properly. This may be of questionable efficacy if traffic is not heavy and the bridge traffic of other pluggable transports is easily able to be excluded by advanced adversarial traffic analysis.

In order to implement a similar defense using a Snowflake proxy (as opposed to a bridge), a custom client needs to be written that would encapsulate your Tor traffic and send it through a TCP WebSocket connection to the Snowflake bridge. This measure is ineffective for the same reasons bridge cover traffic is not. For other traffic to provide effective cover, client traffic needs to be mixed with concurrent, relayed Tor relay traffic; this may require a relatively high speed main network relay to be in use frequently enough to help. Note that website fingerprinting of client traffic is not a severe enough threat to warrant this type of defense for clearnet-destined tor traffic, but it is helpful to protect against end-to-end correlation attacks.

Active Probing

Various jurisdictions utilize active probing in order to block circumvention proxies, including different versions of Tor and the detection and blocking of bridges. Perhaps the most infamous example is the probing system used by the "Great Firewall of China" (GFW). The Tor Project first began exploring this issue in October 2011. At that time it was discovered that:

...connections to US-based Tor bridge relays were being regularly cut off after a very short period of time. At the time we performed some basic experimentation and discovered that Chinese IPs (presumably at the behest of the Great Firewall of China, or GFW) would reach out to the US-based bridge and connect to it shortly after the Tor user in China connected, and, if successful, shortly thereafter the connection would be blocked by the GFW. There wasn't time for a detailed investigation and analysis at the time, but that kernel eventually grew into the investigation detailed below. We were, however, able to determine that limiting connections to the bridge relay to only the single IP expected to be its client would, in fact, block the probes and allow the connection to remain open for an extended period (>48 hours in our testing).

The Tor Project identified two types of probing:

1. Garbage binary probes: when an SSL connection took place, arbitrary binary data was sent to the non-China side of connections originating from China to TCP port 443 (HTTPS). Deep packet inspection (DPI) was suspected because the probe occured soon after the connection was established.
2. Tor probes: China-based Tor clients connecting to US-based bridge relays were probed at 15 minute intervals. The bridge received probes from China-based hosts that: established a TCP connection, performed a SSL negotiation, followed by a SSL renogotiation and the building of a one-hop circuit (including a BEGIN_DIR cell).

To prevent probing, Tor developers then responded by changing the list of supported SSL ciphers included in the "hello" packet sent to Tor clients in China.

Further investigation of the GFW active probing system in 2015 revealed:

• Bridges detected and blocked by the GFW remain blocked. However, a small window of opportunity was available around every 25 hours when Tor clients in China could connect to bridges.
• TCP headers of active probes suggest the thousands of IP addresses are controlled by a single source and not independent computers.
• The GFW also targets other circumvention systems like SoftEther and GoAgent.
• Bridges are probed by the GFW using the standard Tor protocol, as well as obfs2/3.
• Tor probes had increased in frequency from 15 minute intervals to near real-time -- active probes emerged half a second after a bridge connection was established.
• The GFW sensor is unable to reassemble TCP streams.

In 2019, The Tor Project noted:

When the Great Firewall's active probing attack discovered a bridge, the GFW used to block the bridge by its IP address and port, which conveniently left other transport protocols that ran on the same IP address, say obfs4, reachable. This behavior changed recently, and bridges are now blocked by their IP address. This means that a protocol that is vulnerable to the GFW’s active probing attack (e.g., vanilla Tor, fte, and obfs3) can get the entire bridge blocked—including obfs4, which is resistant to active probing! The new BridgeDB release addresses this issue by only handing out a bridge’s probing-resistant protocols if the bridge supports protocols that are both vulnerable and resistant to active probing. For example, if a bridge supports both vanilla Tor and obfs4, then we only hand obfs4 to users.

Research suggests ScrambleSuit and obfs4 can successfully defend against probing attacks, but their ongoing effectiveness will remain an open research question. The take-home message is that Whonix users in heavily censored nations like China and Iran will require an obfs4 bridge or other probe-resistant protocols to try and circumvent censorship.

For further reading on this topic, see:

• Examining How the Great Firewall Discovers Hidden Circumvention Servers
• The Great Firewall’s active probing circumvention technique with portknocking and SDN
• Demystifying the Great Firewall of China
• Analyzing China’s Blocking of Unpublished Tor Bridges
• How the Great Firewall of China is Blocking Tor
• Detecting Probe-resistant Proxies

License

Whonix Bridges wiki page Copyright (C) Amnesia <amnesia at boum dot org>
Whonix Bridges wiki page Copyright (C) 2012 - 2024 ENCRYPTED SUPPORT LP <adrelanos(at)whonix.org (Replace (at) with @.)Please DO NOT use e-mail for one of the following reasons: Private Contact: Please avoid e-mail whenever possible. (Private Communications Policy) User Support Questions: No. (See Support.) Leaks Submissions: No. (No Leaks Policy) Sponsored posts: No. Paid links: No. SEO reviews: No. >

This program comes with ABSOLUTELY NO WARRANTY; for details see the wiki source code.
This is free software, and you are welcome to redistribute it under certain conditions; see the wiki source code for details.

Whonix The most watertight privacy operating system in the world.

Dark mode

Follow us on social media

Supported by Power Up Privacy

Whonix is proudly supported until 2025 by Power Up Privacy, a privacy advocacy group that seeks to supercharge privacy projects with resources so they can complete their mission of making our world a better place. (Strictly subject to our sponsorship policy.)

At Whonix we value freedom and trust, supporting Open Source and Freedom Software

By using this website, you acknowledge you have read, understood, and agree to be bound by these agreements: Terms of Service, Privacy Policy, Cookie Policy, E-Sign Consent, DMCA, Imprint 2012- 2024 ENCRYPTED SUPPORT LP

Your support makes
all the difference!

We believe security software like Whonix needs to remain open source and independent. Would you help sustain and grow the project? Learn more about our 12 year success story and maybe DONATE!