Meek transport issue

Support Censorship Circumvention
2

In modern Tor browser, meek is served by obfs4proxy (bridge called meek_lite). meek-client standalone is considered obsolete, but it works too.

Commands to start:

UseBridges 1
ClientTransportPlugin obfs4,obfs3,meek_lite exec /usr/bin/obfs4proxy -enableLogging=true -logLevel INFO managed
Bridge meek_lite 0.0.2.0:3 97700DFE9F483596DDA6264C4D7DF7641E1E39CE url=https://meek.azureedge.net/ front=ajax.aspnetcdn.com

or

UseBridges 1
ClientTransportPlugin meek exec /usr/bin/meek-client url=https://meek.azureedge.net/ front=ajax.aspnetcdn.com
Bridge meek 0.0.3.0:3 url=https://meek.azureedge.net/ front=ajax.aspnetcdn.com

If you use a distribution with AppArmor (Ubuntu, Debian, openSUSE), you should add these lines and reboot your computer:

sudo nano /etc/apparmor.d/abstractions/tor

/usr/bin/obfsproxy PUx,
/usr/bin/obfs4proxy Pix,
/usr/bin/meek-client ix,
/usr/bin/snowflake-client ix,

I don’t know about SELinux and MSEC.

Try to keep binary files as new as possible and copy with replacement into /usr/bin (I know, this is not good). You can get new binaries from Tor Browser.

2 Likes