Repository navigation
Releases
BoringTun CLI 0.7.1 (WireSock e94c04f3f4fd), build 1 (experimental)
Static boringtun-cli binaries built by this repository from
WireSock BoringTun commit e94c04f3f4fdb8b392f9586db07a269ea0bf7575
(boringtun-cli 0.7.1), build 1, for the experimental userspace
AmneziaWG backend of amneziawg-install.
These archives are meant for amneziawg-install, which installs a BoringTun
release only from the exact URLs and SHA-256 values embedded in an installer
version. Publishing this release does not change the BoringTun release pinned
by existing amneziawg-install versions; adopting it is a separate, reviewed
installer update. The archives are not published or endorsed by the upstream
BoringTun or WireSock BoringTun projects.
| Architecture | Target | Linkage |
|---|---|---|
| x86_64 | x86_64-unknown-linux-musl |
static PIE |
| aarch64 | aarch64-unknown-linux-musl |
static, not position-independent: the binary's own code is not address-randomised |
Built reproducibly with Rust 1.98.1
(cargo build --release --locked -p boringtun-cli, symbols stripped) by the
BoringTun Artifacts workflow, which also attests their build provenance. Each
archive holds the binary, BoringTun's BSD-3-Clause LICENSE,
THIRD-PARTY-LICENSES for the Rust crates compiled into it, and a
MANIFEST with the build provenance and the binary's SHA-256.
Tested on native runners of both architectures, with the daemon in the
foreground, against amneziawg-go (BoringTun's awg-go-interop.sh and
awg31-interop.sh). Interop with the AmneziaWG kernel module has not been
tested with these binaries.
Known advisory: RUSTSEC-2025-0069 reports that daemonize 0.5.0, a
dependency of boringtun-cli, is unmaintained. It is not a disclosed
vulnerability. The crate runs only when boringtun-cli daemonizes itself,
and amneziawg-install runs it exclusively in the foreground.
Verify the archives with sha256sum -c SHA256SUMS:
a2d7c4a0cc702a7dfc146036e6bda6e341701a3609a6842462bfdbebf7490880 boringtun-cli-0.7.1-ge94c04f3f4fd-linux-aarch64-musl.tar.gz
6614814d11cbec37cf65c40887822af9866ac5abc05929332968737c39c6af68 boringtun-cli-0.7.1-ge94c04f3f4fd-linux-x86_64-musl.tar.gz
and the build provenance of each archive with the GitHub CLI. The
certificate identity must match exactly, and the source digest is the
amneziawg-install commit whose BoringTun Artifacts run built the archives
(not the BoringTun source commit above):
gh attestation verify <archive> \
--repo wiresock/amneziawg-install \
--cert-identity \
https://github.com/wiresock/amneziawg-install/.github/workflows/boringtun-artifacts.yml@refs/heads/main \
--source-digest 8f426268955516845fc34427589dc37012eff71d \
--source-ref refs/heads/main \
--deny-self-hosted-runners
Binary SHA-256 (binary_sha256 in each MANIFEST):
7c717357554a4d8022154fbdb1c40c92de8174ee064e81878fdf5f610651fb79 x86_64 boringtun-cli
cc1cdf215bb3d75f8a7006f8d424d698e9574dadb3e08becd8ace17a3c44cb08 aarch64 boringtun-cli
BoringTun CLI 0.7.1 (WireSock b94943906b11), build 1 (experimental)
Static boringtun-cli binaries built by this repository from
WireSock BoringTun commit b94943906b11641e274b3c950cc905aaf1631c59
(boringtun-cli 0.7.1), build 1, for the experimental userspace
AmneziaWG backend of amneziawg-install.
These archives are meant for amneziawg-install, which installs a BoringTun
release only from the exact URLs and SHA-256 values embedded in an installer
version. Publishing this release does not change the BoringTun release pinned
by existing amneziawg-install versions; adopting it is a separate, reviewed
installer update. The archives are not published or endorsed by the upstream
BoringTun or WireSock BoringTun projects.
| Architecture | Target | Linkage |
|---|---|---|
| x86_64 | x86_64-unknown-linux-musl |
static PIE |
| aarch64 | aarch64-unknown-linux-musl |
static, not position-independent: the binary's own code is not address-randomised |
Built reproducibly with Rust 1.98.1
(cargo build --release --locked -p boringtun-cli, symbols stripped) by the
BoringTun Artifacts workflow, which also attests their build provenance. Each
archive holds the binary, BoringTun's BSD-3-Clause LICENSE,
THIRD-PARTY-LICENSES for the Rust crates compiled into it, and a
MANIFEST with the build provenance and the binary's SHA-256.
Tested on native runners of both architectures, with the daemon in the
foreground, against amneziawg-go (BoringTun's awg-go-interop.sh and
awg31-interop.sh). Interop with the AmneziaWG kernel module has not been
tested with these binaries.
Known advisory: RUSTSEC-2025-0069 reports that daemonize 0.5.0, a
dependency of boringtun-cli, is unmaintained. It is not a disclosed
vulnerability. The crate runs only when boringtun-cli daemonizes itself,
and amneziawg-install runs it exclusively in the foreground.
Verify the archives with sha256sum -c SHA256SUMS:
cf65174fcb25095a2637544fda860d5d033cd4d271ee7ac40e8f457ece75ecce boringtun-cli-0.7.1-gb94943906b11-linux-aarch64-musl.tar.gz
c6a39a50ccc89f6ac4107d3fe0d530a6f83badc11b405617195e65092e96e7fb boringtun-cli-0.7.1-gb94943906b11-linux-x86_64-musl.tar.gz
and the build provenance of each archive with the GitHub CLI. The
certificate identity must match exactly, and the source digest is the
amneziawg-install commit whose BoringTun Artifacts run built the archives
(not the BoringTun source commit above):
gh attestation verify <archive> \
--repo wiresock/amneziawg-install \
--cert-identity \
https://github.com/wiresock/amneziawg-install/.github/workflows/boringtun-artifacts.yml@refs/heads/main \
--source-digest 41fe7d903f1903fc5962baf53b551a2dc27aad15 \
--source-ref refs/heads/main \
--deny-self-hosted-runners
Binary SHA-256 (binary_sha256 in each MANIFEST):
1210a3c6780948ea07f301c4fa022c0b4ab634da71db0053f65757c8683470d5 x86_64 boringtun-cli
c6752410b3994007a9ace5f2d93c30c009b2d7478ebed27b01aacc6168a08629 aarch64 boringtun-cli
BoringTun CLI 0.7.1 (WireSock ae2ab44e9a68), build 1 (experimental)
Static boringtun-cli binaries built by this repository from
WireSock BoringTun commit ae2ab44e9a68ca1a3232d2e8b13f9db30a9b9dcf
(boringtun-cli 0.7.1), build 1, for the experimental userspace
AmneziaWG backend of amneziawg-install.
These archives are meant for amneziawg-install, which installs a BoringTun
release only from the exact URLs and SHA-256 values embedded in an installer
version. Publishing this release does not change the BoringTun release pinned
by existing amneziawg-install versions; adopting it is a separate, reviewed
installer update. The archives are not published or endorsed by the upstream
BoringTun or WireSock BoringTun projects.
| Architecture | Target | Linkage |
|---|---|---|
| x86_64 | x86_64-unknown-linux-musl |
static PIE |
| aarch64 | aarch64-unknown-linux-musl |
static, not position-independent: the binary's own code is not address-randomised |
Built reproducibly with Rust 1.98.1
(cargo build --release --locked -p boringtun-cli, symbols stripped) by the
BoringTun Artifacts workflow, which also attests their build provenance. Each
archive holds the binary, BoringTun's BSD-3-Clause LICENSE,
THIRD-PARTY-LICENSES for the Rust crates compiled into it, and a
MANIFEST with the build provenance and the binary's SHA-256.
Tested on native runners of both architectures, with the daemon in the
foreground, against amneziawg-go (BoringTun's awg-go-interop.sh and
awg31-interop.sh). Interop with the AmneziaWG kernel module has not been
tested with these binaries.
Known advisory: RUSTSEC-2025-0069 reports that daemonize 0.5.0, a
dependency of boringtun-cli, is unmaintained. It is not a disclosed
vulnerability. The crate runs only when boringtun-cli daemonizes itself,
and amneziawg-install runs it exclusively in the foreground.
Verify the archives with sha256sum -c SHA256SUMS:
865e9aebcb6d3a28f4618f98e14fa667ecc7ceb47440f3a5e96be8e7ded9f50b boringtun-cli-0.7.1-gae2ab44e9a68-linux-aarch64-musl.tar.gz
d509a73ef26b9b560e2b836709f0ab4332edde06f12d77a03a1ac31fe4d3a221 boringtun-cli-0.7.1-gae2ab44e9a68-linux-x86_64-musl.tar.gz
and the build provenance of each archive with the GitHub CLI. The
certificate identity must match exactly, and the source digest is the
amneziawg-install commit whose BoringTun Artifacts run built the archives
(not the BoringTun source commit above):
gh attestation verify <archive> \
--repo wiresock/amneziawg-install \
--cert-identity \
https://github.com/wiresock/amneziawg-install/.github/workflows/boringtun-artifacts.yml@refs/heads/main \
--source-digest d451c19cda248068c73c5ba2446b54e2852788d2 \
--source-ref refs/heads/main \
--deny-self-hosted-runners
Binary SHA-256 (binary_sha256 in each MANIFEST):
ad23145661408732b9e04b6edad6730134ef5fa06637f50892d1e46d523970e7 x86_64 boringtun-cli
32239dd79858f58a8cad1e3782c7867dc9d71c6ebe098410d184367eef95cf21 aarch64 boringtun-cli
BoringTun CLI 0.7.1 (WireSock 71d88784ad29), build 1 (experimental)
Static boringtun-cli binaries built by this repository from
WireSock BoringTun commit 71d88784ad29dc95871c105e26cc62f6acdd565b
(boringtun-cli 0.7.1), build 1, for the experimental userspace
AmneziaWG backend of amneziawg-install.
These archives are meant for amneziawg-install, which checks them against
SHA-256 values embedded in the installer. They are not published or endorsed
by the upstream BoringTun or WireSock BoringTun projects. At the time of this
release, amneziawg-install does not yet install BoringTun.
| Architecture | Target | Linkage |
|---|---|---|
| x86_64 | x86_64-unknown-linux-musl |
static PIE |
| aarch64 | aarch64-unknown-linux-musl |
static, not position-independent: the binary's own code is not address-randomised |
Built reproducibly with Rust 1.98.1
(cargo build --release --locked -p boringtun-cli, symbols stripped) by the
BoringTun Artifacts workflow, which also attests their build provenance. Each
archive holds the binary, BoringTun's BSD-3-Clause LICENSE,
THIRD-PARTY-LICENSES for the Rust crates compiled into it, and a
MANIFEST with the build provenance and the binary's SHA-256.
Tested on native runners of both architectures, with the daemon in the
foreground, against amneziawg-go (BoringTun's awg-go-interop.sh and
awg31-interop.sh). Interop with the AmneziaWG kernel module has not been
tested with these binaries.
Known advisory: RUSTSEC-2025-0069 reports that daemonize 0.5.0, a
dependency of boringtun-cli, is unmaintained. It is not a disclosed
vulnerability. The crate runs only when boringtun-cli daemonizes itself,
and amneziawg-install runs it exclusively in the foreground.
Verify the archives with sha256sum -c SHA256SUMS:
7ad1e2b6c24d667b2e39ed6ad4620f1dfb94de3cf648a9733dcff3625559305d boringtun-cli-0.7.1-g71d88784ad29-linux-aarch64-musl.tar.gz
f519b535b177d703e4b1a64610943a69c040a858364fa995c311e29a5db17630 boringtun-cli-0.7.1-g71d88784ad29-linux-x86_64-musl.tar.gz
and the build provenance of each archive with the GitHub CLI. The
certificate identity must match exactly, and the source digest is the
amneziawg-install commit whose BoringTun Artifacts run built the archives
(not the BoringTun source commit above):
gh attestation verify <archive> \
--repo wiresock/amneziawg-install \
--cert-identity \
https://github.com/wiresock/amneziawg-install/.github/workflows/boringtun-artifacts.yml@refs/heads/main \
--source-digest 987db34de077c445c1193412e87c4a0d4c956bc1 \
--source-ref refs/heads/main \
--deny-self-hosted-runners
Binary SHA-256 (binary_sha256 in each MANIFEST):
127b633d0b98568d8f686421ea8b3a4133de260e49de71cc470008759cf78721 x86_64 boringtun-cli
16b04cbebc3ba5fe45e8d5c940620522ed49d731642791e84368bfa393509c6b aarch64 boringtun-cli