v0.3.0

Airlock is self-hosted, end-to-end encrypted file transfer between your own
devices, over your Tailscale network. One binary, an installable web app, no
accounts and no public port.

Which file do I want

Your machine	Download
Linux, most PCs and servers	airlock_v0.3.0_linux_amd64
Linux on a Pi or an ARM VPS	airlock_v0.3.0_linux_arm64
Mac, Apple silicon	airlock_v0.3.0_darwin_arm64
Mac, Intel	airlock_v0.3.0_darwin_amd64
Windows	airlock_v0.3.0_windows_amd64.exe
Windows on ARM	airlock_v0.3.0_windows_arm64.exe

Getting started

curl -LO https://github.com/ahnafnafee/airlock/releases/download/v0.3.0/airlock_v0.3.0_linux_amd64
curl -LO https://github.com/ahnafnafee/airlock/releases/download/v0.3.0/SHA256SUMS
sha256sum --check --ignore-missing SHA256SUMS
chmod +x airlock_v0.3.0_linux_amd64
./airlock_v0.3.0_linux_amd64

It prints the one URL that works. Open it on any device on your tailnet,
choose a passphrase, and send a file. That is the whole setup.

You need Tailscale on at least two devices, and
HTTPS certificates enabled on
your tailnet. Airlock needs a real certificate because the browser needs a
secure context: without one there is no Web Crypto and no service worker, and
the client cannot work at all.

Setup, options and the security model are in the
README.

Verifying a download

Every binary ships its own .sha256, and SHA256SUMS carries all six.

---

What's Changed

• fix(push): deliver Android notifications with the app closed by @ahnafnafee in #4
• fix(windows): stage arbitrary context-menu files by @ahnafnafee in #5

Full Changelog: v0.2.0...v0.3.0

v0.2.0

Airlock is self-hosted, end-to-end encrypted file transfer between your own
devices, over your Tailscale network. One binary, an installable web app, no
accounts and no public port.

Which file do I want

Your machine	Download
Linux, most PCs and servers	airlock_v0.2.0_linux_amd64
Linux on a Pi or an ARM VPS	airlock_v0.2.0_linux_arm64
Mac, Apple silicon	airlock_v0.2.0_darwin_arm64
Mac, Intel	airlock_v0.2.0_darwin_amd64
Windows	airlock_v0.2.0_windows_amd64.exe
Windows on ARM	airlock_v0.2.0_windows_arm64.exe

Getting started

curl -LO https://github.com/ahnafnafee/airlock/releases/download/v0.2.0/airlock_v0.2.0_linux_amd64
curl -LO https://github.com/ahnafnafee/airlock/releases/download/v0.2.0/SHA256SUMS
sha256sum --check --ignore-missing SHA256SUMS
chmod +x airlock_v0.2.0_linux_amd64
./airlock_v0.2.0_linux_amd64

It prints the one URL that works. Open it on any device on your tailnet,
choose a passphrase, and send a file. That is the whole setup.

You need Tailscale on at least two devices, and
HTTPS certificates enabled on
your tailnet. Airlock needs a real certificate because the browser needs a
secure context: without one there is no Web Crypto and no service worker, and
the client cannot work at all.

Setup, options and the security model are in the
README.

Verifying a download

Every binary ships its own .sha256, and SHA256SUMS carries all six.

---

What's Changed

• feat: make a transfer finish at the speed the link can carry by @ahnafnafee in #2
• fix(web): keep a file's extension when a save is numbered by @ahnafnafee in #3

Full Changelog: v0.1.0...v0.2.0

v0.1.0

Airlock is self-hosted, end-to-end encrypted file transfer between your own
devices, over your Tailscale network. One binary, an installable web app, no
accounts and no public port.

Which file do I want

Your machine	Download
Linux, most PCs and servers	airlock_v0.1.0_linux_amd64
Linux on a Pi or an ARM VPS	airlock_v0.1.0_linux_arm64
Mac, Apple silicon	airlock_v0.1.0_darwin_arm64
Mac, Intel	airlock_v0.1.0_darwin_amd64
Windows	airlock_v0.1.0_windows_amd64.exe
Windows on ARM	airlock_v0.1.0_windows_arm64.exe

Getting started

curl -LO https://github.com/ahnafnafee/airlock/releases/download/v0.1.0/airlock_v0.1.0_linux_amd64
curl -LO https://github.com/ahnafnafee/airlock/releases/download/v0.1.0/SHA256SUMS
sha256sum --check --ignore-missing SHA256SUMS
chmod +x airlock_v0.1.0_linux_amd64
./airlock_v0.1.0_linux_amd64

It prints the one URL that works. Open it on any device on your tailnet,
choose a passphrase, and send a file. That is the whole setup.

You need Tailscale on at least two devices, and
HTTPS certificates enabled on
your tailnet. Airlock needs a real certificate because the browser needs a
secure context: without one there is no Web Crypto and no service worker, and
the client cannot work at all.

Setup, options and the security model are in the
README.

Verifying a download

Every binary ships its own .sha256, and SHA256SUMS carries all six.

---

What's Changed

• feat: Airlock, encrypted file transfer between your own devices by @ahnafnafee in #1

New Contributors

• @ahnafnafee made their first contribution in #1

Full Changelog: https://github.com/ahnafnafee/airlock/commits/v0.1.0