Bouncer 0.5.6
Version 0.5.6 was built and tested, but has no GitLab release (checked on
17 November 2026). Builds exist for Android, Windows, the command
line and the server. They weren't published or rolled out to
production. Both apps show 0.5.6+33 under Settings > About. On
Android the version code is 33. On Windows, the portable ZIP and the
test-signed installer (package version 0.5.33.0) are the build.
There's no iPhone or Mac build of 0.5.6.
For administrators: the server stays up while OpenBao isn't ready
A server from this release behaves differently when OpenBao is sealed.
Before, the server exited and restarted in a loop, and everyone saw "502".
Now it stays up and answers 503 with backend_sealed,
backend_unreachable or backend_auth_failed, /v1/health included, until
OpenBao is ready. It issues nothing meanwhile, but still accepts revokes and
cancels. It notices by itself once OpenBao is unsealed. Unsealing is still
yours to do.
- A monitor on
/v1/healthsees 503 with one of those codes, not 502. - The container shows unhealthy meanwhile, and Docker doesn't restart it.
BOUNCER_WAIT_FOR_OPENBAOis now ignored. Remove it from.env.- The
bouncercommand line exits 12 to 15 for these outages, where it used to exit 1.
When Bouncer is unavailable explains each message and who acts.
Fixed in this build
The apps say why Bouncer is unavailable
When the server can't serve, the apps say so by name, for example "Your Bouncer server's vault is sealed", and that there's nothing to fix on your device. See Troubleshooting.
Why a device can't approve, and which one can
Where a request needs a key kept in secure hardware that asks for your fingerprint or face, Windows says so, names your devices that have such a key, and offers only Deny. A phone whose key doesn't qualify shows the same notice, with Approve turned off. See Answer requests.
Pair this PC checks the server first
On Windows, Bouncer checks the server's address, certificate and API before it sends the pairing code, and Details shows the certificate. The setup and offline messages no longer assume Tailscale. See Pair the app with your server.
The server download
The server's files come with their own sums file,
bouncer-server-0.5.6+33-SHA256SUMS, so you can check them without the rest
of the release. See Get Bouncer.
Upgrading
- Android: the update installs over the earlier internal builds and keeps your pairing.
- Windows portable: unzip 0.5.6 into a new folder next to the old one, and keep the old folder to go back to. Your pairing carries over.
- Windows installer: installs over 0.5.32.0 and keeps your pairing.
- Server: no migration. The app fixes don't need a server upgrade.
Known issues
- Automatic unsealing isn't live yet. After a reboot, OpenBao still has to be unsealed by hand.
- A Windows Hello key can't meet a secure-hardware policy yet. Checking the PC's security chip (TPM attestation) is not in this release. From the private 0.5.7 release, the server checks a TPM attestation at enrolment when Windows supplies one, but no real PC has passed that check yet, and keys enrolled before it stay unchecked.
- Windows Hello closing by itself when a request is decided elsewhere has been tested only with automated tests, not with a real Windows Hello PIN.
What was checked, and on what
-
Automated tests for every fix, before this build was made.
-
Pre-release checks passed for the Windows MSIX, portable app and CLI on a test machine, the Linux CLI, and the server download against a throwaway OpenBao with fake data. These checks don't include the signed Android build. It needs its own check, because a check of an unsigned build doesn't cover it.
-
As checked on 17 November 2026, the Bouncer project's own production server runs build
0.3.8+25. These source changes are not deployed there. -
On 18 November 2026, the 0.5.6 internal Android build was on Firebase for S6 Studios' own testing only. See Platforms and status.