Source: rust-signal-tlsd
Section: net
Build-Depends: debhelper-compat (= 13),
 dh-sequence-cargo,
 help2man,
 libdebhelper-perl
Build-Depends-Arch: cargo:native,
 rustc:native,
 libstd-rust-dev,
 librust-anyhow-1+default-dev,
 librust-arc-swap-1+default-dev,
 librust-clap-4+derive-dev,
 librust-clap-4+env-dev,
 librust-clap-4+error-context-dev,
 librust-clap-4+help-dev,
 librust-clap-4+std-dev,
 librust-env-logger-0.11-dev,
 librust-log-0.4+default-dev,
 librust-tokio-1+default-dev (>= 1.50),
 librust-tokio-1+fs-dev (>= 1.50),
 librust-tokio-1+io-util-dev (>= 1.50),
 librust-tokio-1+macros-dev (>= 1.50),
 librust-tokio-1+net-dev (>= 1.50),
 librust-tokio-1+rt-multi-thread-dev (>= 1.50),
 librust-tokio-1+signal-dev (>= 1.50),
 librust-tokio-1+sync-dev (>= 1.50),
 librust-tokio-1+time-dev (>= 1.50),
 librust-tokio-rustls-0.26+default-dev,
 librust-tokio-rustls-0.26+ring-dev
Maintainer: Debian Rust Maintainers <pkg-rust-maintainers@alioth-lists.debian.net>
Uploaders:
 kpcyrd <git@rxv.cc>
Standards-Version: 4.7.3
Vcs-Git: https://salsa.debian.org/rust-team/debcargo-conf.git [src/signal-tlsd]
Vcs-Browser: https://salsa.debian.org/rust-team/debcargo-conf/tree/master/src/signal-tlsd
Homepage: https://github.com/kpcyrd/signal-tlsd
X-Cargo-Crate: signal-tlsd
X-Cargo-Crate-Version: 0.1.0

Package: signal-tlsd
Architecture: any
Section: net
Depends:
 ${misc:Depends},
 ${shlibs:Depends},
 ${cargo:Depends}
Recommends:
 ${cargo:Recommends}
Suggests:
 ${cargo:Suggests}
Provides:
 ${cargo:Provides}
Built-Using: ${cargo:Built-Using}
Static-Built-Using: ${cargo:Static-Built-Using}
Description: Standalone Rust implementation of Signal's domain fronting TLS proxy
 Negotiates an outer TLS handshake and listens for an incoming TLS connection
 from the Signal client. The inner TLS connection remains end-to-end encrypted
 between the client and the Signal server, while the outer TLS connection is
 terminated at the proxy.
 .
 This evades censorship based on IP address blocking, DNS filtering, and
 SNI-based deep packet inspection.
 .
 It implements the protocol of the official Signal-TLS-Proxy, but in a single
 process instead of two nginx instances glued together with docker-compose.
 .
 It was successfully field-tested in April 2026 to evade Russian censorship of
 Signal, through a VPS located in Kazakhstan.