MEEK-CLIENT(1)

📦 version 0.38.0, in alpine 3.24, arch rolling, nixos 26.05, nixpkgs unstable

💅 MEEK-CLIENT(1) 💅

okay bestie, buckle up — this is the manual page for meek-client, and we're gonna get through every single detail together, no cap. 🫶

🌸 NAME 🌸

meek-client — the meek client transport plugin. literally iconic behavior. ✨

✨ SYNOPSIS ✨

meek-client [OPTIONS]

🦋 DESCRIPTION 🦋

okay so meek-client is a transport plugin for Tor that encodes a stream as a sequence of HTTP requests and responses. it has a url option to control what destination server requests are directed to, and a front option for domain name camouflage: the domain name in the URL is replaced by the front domain before the request is made, but the Host header inside the HTTP request still points to the original domain. the idea is to front through a domain that is not blocked to a domain that is blocked. very main character energy, tbh. 💅

🧚 CONFIGURATION 🧚

configuration for meek-client usually happens in a torrc file. yes bestie, that's the vibe. 🎀

per-bridge options are configured with SOCKS args (key=value pairs in a Bridge line). the possible SOCKS args are:

  • url=URL (required) — the URL of a meek-server instance. the domain name component will typically be hidden by the value in the front arg.
  • front=DOMAIN — front domain name. if provided, this domain name will replace the domain name of url in the DNS request and TLS SNI field. the URL's true domain name will still appear in the Host header of HTTP requests.
  • utls=CLIENTHELLOID — use the uTLS library with the named TLS fingerprint for TLS camouflage. this arg is incompatible with the --helper command line option. the possible values of CLIENTHELLOID are:
    • HelloRandomizedALPN
    • HelloRandomizedNoALPN
    • HelloFirefox_55
    • HelloFirefox_56
    • HelloFirefox_63
    • HelloFirefox_65
    • HelloFirefox_99
    • HelloFirefox_102
    • HelloFirefox_105
    • HelloFirefox_Auto = HelloFirefox_105
    • HelloChrome_58
    • HelloChrome_62
    • HelloChrome_70
    • HelloChrome_72
    • HelloChrome_83
    • HelloChrome_87
    • HelloChrome_96
    • HelloChrome_100
    • HelloChrome_102
    • HelloChrome_Auto = HelloChrome_102
    • HelloIOS_11_1
    • HelloIOS_12_1
    • HelloIOS_13
    • HelloIOS_14
    • HelloIOS_Auto = HelloIOS_14
    • HelloEdge_85
    • HelloEdge_Auto = HelloEdge_85
    • HelloSafari_16_0
    • HelloSafari_Auto = HelloSafari_16_0
    • Hello360_7_5
    • Hello360_Auto = Hello360_7_5
    • HelloQQ_11_1
    • HelloQQ_Auto = HelloQQ_11_1

as a special case, the values none and HelloGolang are recognized as aliases for omitting the utls SOCKS arg; i.e., use native Go TLS. 🦋

for backward compatibility, each SOCKS arg also has an equivalent command line option. for example, this configuration using SOCKS args:

Bridge meek 0.0.2.0:1 url=https://forbidden.example/ front=allowed.example
ClientTransportPlugin meek exec ./meek-client

is the same as this one using command line options:

Bridge meek 0.0.2.0:1
ClientTransportPlugin meek exec ./meek-client --url=https://forbidden.example/ --front=allowed.example

SOCKS args are preferred over command line options because they allow you to have multiple Bridge lines with different settings. if a SOCKS arg and a command line option are both given for the same setting, the SOCKS arg takes precedence. periodt. 💅

the global --helper option prevents meek-client from doing any network operations itself. rather, it will send all requests through a browser extension, which must be set up separately. 🧚

a global proxy (applies to all Bridge lines) can be configured using special torrc options:

Socks4Proxy localhost:1080
Socks5Proxy localhost:1080
Socks5ProxyUsername username
Socks5ProxyPassword password
HTTPSProxy localhost:8080
HTTPSProxyAuthenticator username:password

or, equivalently, using the --proxy command line option. the command line option takes precedence. ✨

when the --helper option is used, you can use proxies of type http, socks4a, or socks5, but you cannot use a username or password with the proxy. without --helper, you can use proxies of type http, https, or socks5, and you can optionally use a username and password. okay? okay. 💖

💅 OPTIONS 💅

  • --front=DOMAIN — front domain name. prefer using the front SOCKS arg on a bridge line over using this command line option.
  • --helper=ADDRESS — address of HTTP helper browser extension. for example, --helper=127.0.0.1:7000.
  • --proxy=URL — URL of upstream proxy. for example, --proxy=http://localhost:8080/, --proxy=socks4a://localhost:1080, or --proxy=socks5://localhost:1080. can also be configured using the HTTPSProxy, Socks4Proxy, or Socks5Proxy options in a torrc file.
  • --log=FILENAME — name of a file to write log messages to (default stderr).
  • --url=URL — URL to correspond with. prefer using the url SOCKS arg on a bridge line over using this command line option.
  • --utls=CLIENTHELLOID — use uTLS with the given TLS fingerprint for TLS camouflage. this option is incompatible with --helper. prefer using the utls SOCKS arg over using this command line option.
  • -h, --help — display a help message and exit. slay. 👑

🔥 SEE ALSO 🔥

https://trac.torproject.org/projects/tor/wiki/doc/meek — go read, bestie. 📚💖

💀 BUGS 💀

please report at https://trac.torproject.org/projects/tor. not me having to tell you where to file bugs, but here we are. 💀

xoxo, your terminal bestie 🫶 — manual MEEK-CLIENT(1), dated 10/20/2022 🌈✨

📦 where this page comes from