Reference
Verify your download
Check that a Teitunnel download is authentic: SHA-256 checksums, GitHub build provenance and code signatures.
Every release lists the SHA-256 of each file in SHA256SUMS.txt, and each file carries
GitHub build provenance: a signed statement of the workflow run and commit that built it.
Checksum
Download SHA256SUMS.txt from the same release, then compare:
shasum -a 256 -c SHA256SUMS.txt --ignore-missingBuild provenance
With the GitHub CLI:
gh attestation verify Teitunnel_0.1.0_universal.dmg --repo teispace/teitunnelIt succeeds only for a file built by Teitunnel's release workflow from this repository.
The Docker image (teispace/teitunnel on Docker Hub and ghcr.io/teispace/teitunnel, the
same digest) is attested the same way, and is built from the release's own teitunnel
after its checksums and provenance are checked:
gh attestation verify oci://ghcr.io/teispace/teitunnel:0.1.0 --repo teispace/teitunnelHomebrew installs the same files: the cask and formula take their checksums from the
release's SHA256SUMS.txt after verifying its provenance, and Homebrew checks each download
against them.
Signatures
- macOS:
spctl -a -vv /Applications/Teitunnel.appshould saysource=Notarized Developer ID. - Updates are verified by the app itself against the key built into it, before they're installed.
Last updated on
Security
How Teitunnel protects your Cloudflare credentials, your DNS records, your computer and your traffic, what it stores where, and what it never keeps.
Limits and costs
What each Teitunnel feature costs on Cloudflare and which limits apply — Quick Tunnels, Cloudflare Tunnel, Zero Trust, Workers, D1, WAF, Transform and Cache Rules, analytics — with the free plan's numbers and when they were checked.