# meek mit Homebrew, apk, Nix, pacman installieren Prüfe Installationswege, Executables, Metadaten und Sicherheitshinweise für meek in AI-Agent-Workflows. ## Installation ```sh sudo av install brew:meek ``` Weitere Installationsbefehle: ### macOS - Homebrew (100%): ```sh brew install meek ``` Evidenz: local Homebrew formula metadata ### Linux - apk (92%): ```sh sudo apk add meek ``` Evidenz: Alpine Linux edge package indexes: meek from https://dl-cdn.alpinelinux.org/alpine/edge/community/x86_64/APKINDEX.tar.gz - Nix (92%): ```sh nix profile install nixpkgs#meek ``` Evidenz: nixpkgs package indexes: pkgs/by-name/me/meek/package.nix from https://api.github.com/repos/NixOS/nixpkgs/git/trees/master?recursive=1 - pacman (92%): ```sh sudo pacman -S meek ``` Evidenz: Arch Linux sync databases: meek from https://geo.mirror.pkgbuild.com/extra/os/x86_64/extra.db.tar.gz ## Paketfakten - **Paketschlüssel:** brew:meek - **Paketmanager:** Homebrew - **Version:** 0.38.0 - **Quellzusammenfassung:** Blocking-resistant pluggable transport for Tor - **Homepage:** - **Generiert:** 2026-08-03T19:37:03+00:00 ## Executables - meek-client (Alias) - meek-server (Alias) ## Installationsverhalten - Bottle: nicht verfügbar ## Version und Aktualität - Seite generiert: 2026-08-03 - Manager-Version: 0.38.0 ## Projektgeschichte und Nutzung meek is a Tor pluggable transport designed to resist blocking by encoding traffic as HTTPS requests and responses reflected through hard-to-block third-party web services. Its README identifies domain fronting as the key trick behind the transport. ### Projektgeschichte The official tag history reaches back to 0.0 in February 2014 and 0.1 in March 2014, with David Fifield as the author on early commits. The current Tor GitLab project was created in June 2020 as part of Tor's anti-censorship pluggable-transports namespace, preserving a project with older history. The README explains the architecture: `meek-client` runs on the censored client, `meek-server` runs on a Tor relay, and reflector components for App Engine, nginx, PHP, WSGI, and browser-extension helpers make HTTPS traffic look like allowed web traffic. ### Adoptionsgeschichte meek's adoption is tied to Tor Browser's censorship-circumvention workflow, where pluggable transports help users connect when direct Tor access is blocked. The Tor support documentation keeps circumvention guidance under Tor Browser support, while the package input shows meek available in Homebrew, Alpine, Nix, and Arch. Its deployment history is also shaped by changing support for domain fronting among large providers, so meek is best understood as one member of Tor's anti-censorship transport family rather than a general-purpose proxy. ### Wie es verwendet wird Users normally encounter meek through Tor pluggable-transport configuration rather than by hand-running it. The README documents direct client usage with `meek-client --url=... --front=...`, server-side `meek-server`, and helper components for reflector services and browser-based TLS camouflage. ### Warum Paket-Nerds sich dafür interessieren meek is significant because it packages anti-censorship research into small Unix-style client and server binaries. For packagers, it is a privacy-networking tool whose value comes from predictable executable names, Tor integration, and minimal visible configuration rather than from broad standalone CLI features. ### Zeitleiste - 2014: Official tag 0.0 is created in February, followed by 0.1 in March. - 2020: Current Tor GitLab project is created in the anti-censorship pluggable-transports namespace. - 2022: Official tag v0.38.0 is created. ### Related projects - meek is part of Tor's pluggable-transport ecosystem and relates to Tor Browser, Tor bridges, domain fronting, App Engine reflectors, nginx/PHP/WSGI reflectors, and browser-extension TLS camouflage. ### Quellen - - - - - ## Sicherheitshinweise broad file, network, media, or database tool signal. - **Geiger-Risiko:** blue / mittel - broad file, network, media, or database tool signal ## Andere Paketmanager-Einträge - Nix - meek: normalized package name match | nixpkgs package indexes: pkgs/by-name/me/meek/package.nix from https://api.github.com/repos/NixOS/nixpkgs/git/trees/master?recursive=1 - apk - meek - 0.38.0-r24: normalized package name match | Alpine Linux edge package indexes: meek from https://dl-cdn.alpinelinux.org/alpine/edge/community/x86_64/APKINDEX.tar.gz | Pluggable transport proxy written in Go | https://trac.torproject.org/projects/tor/wiki/doc/meek - apk - meek-doc - 0.38.0-r24: normalized package name match | Alpine Linux edge package indexes: meek-doc from https://dl-cdn.alpinelinux.org/alpine/edge/community/x86_64/APKINDEX.tar.gz | Pluggable transport proxy written in Go (documentation) | https://trac.torproject.org/projects/tor/wiki/doc/meek - apk - meek-server - 0.38.0-r24: normalized package name match | Alpine Linux edge package indexes: meek-server from https://dl-cdn.alpinelinux.org/alpine/edge/community/x86_64/APKINDEX.tar.gz | meek pluggable transport proxy server | https://trac.torproject.org/projects/tor/wiki/doc/meek - pacman - meek - 0.38.0-3: normalized package name match | Arch Linux sync databases: meek from https://geo.mirror.pkgbuild.com/extra/os/x86_64/extra.db.tar.gz | A pluggable transport proxy written in Go | https://trac.torproject.org/projects/tor/wiki/doc/meek ## Combined YAML source View the package source record on GitHub. [combined/meek.yml](https://github.com/mxcl/pkgdb/blob/main/combined/meek.yml) ## Quellen - pkg.so package database - Geiger risk classifier - curated package history - pkgdb category and tag curation - external package-manager database matches - cross-ecosystem install command graph