Keyboard shortcuts

Press ← or → to navigate between chapters

Press S or / to search in the book

Press ? to show this help

Press Esc to hide this help

Manual for Bouncer 0.5.9. Chapters state version and distribution limits. Source d8dfc7c, site build 22 November 2026. Your server or app may run an earlier version.

On this page

Bouncer 0.5.8

Published as a private GitLab release, v0.5.8+35, from commit 0a7de11a810e4bf8d8b235caaec97cde6034108b. It has 21 files, all checked against their SHA256 hashes after upload. The source repository and release are private. The Android internal build is on Firebase App Distribution and iOS 0.5.8 is in internal TestFlight, both for S6 Studios' own testing. Updating a client doesn't upgrade its server. The Bouncer project's own production server was still running build 0.3.8+25 when this release was published. It was upgraded to 0.5.8+35 on 21 November 2026.

Bouncer 0.5.8 has changes for Android, iPhone, Windows, the command line and the server. The apps show 0.5.8+35 under Settings > About, and bouncer --version prints bouncer 0.5.8+35 (bouncer.v1).

Before you upgrade a server: it applies database migration 0020, and any resource that sets require_hardware_key will stop accepting approvals from iPhones, Macs and Android phones without verified key attestation. Read For operators first.

Changes in the apps

  • Privacy policy and Support in Settings. Settings has two new rows on Android, iPhone and Windows, and they work while the server is offline. Each opens the page in your browser. If the browser can't open it, Bouncer shows the address with a Copy button.
  • Clearer wording in the apps. The Settings card called "This is a pre-release" is now "What protects your approvals", and still says who can approve on that device. On Windows, a key the server hasn't verified now reads "The server hasn't verified that the key is kept in this PC's security chip (TPM)". When you approve saving a secret, the note on where the values go now says what OpenBao is. The version under About still ends in "(pre-release)".
  • Fewer false "Can't reach" messages on Android (#291). If the connection drops briefly just before you open Bouncer, the app shows "Reconnecting…" for up to 4 seconds instead of "Can't reach your Bouncer server". A real outage still shows as offline after that.
  • Windows checks for new requests when you show it (#290). Showing Bouncer Desktop from the tray, or restoring it from the taskbar, now checks your server for new requests straight away.
  • Requests that need a verified hardware key (#282). Some resources need a key the server has verified is kept in secure hardware. Your phone or PC now goes by what the server has verified about its key, not by the key's own label. If the server hasn't verified it, Bouncer says "The server hasn't verified this phone's key, so it can't approve this request", offers only Deny, and suggests asking an administrator or using a device the server has verified. Viewing a credential that needs such a key works the same way. The server can't verify an iPhone's key, so an iPhone can only deny these requests. If your server is older than 0.5.8, the apps offer only Deny for them.
  • Stale Android notifications are withdrawn (#289). If a phone misses the push that closes a request, the alert used to stay. Now, when Bouncer starts, comes back to the front, the phone is unlocked or the inbox refreshes, Bouncer asks your server about the request alerts it's showing and removes those for requests that have ended. It never removes an alert for a request that's still waiting.
  • Windows install guide. The guide that comes with the installer, bouncer-windows-install-instructions.md, is now titled "Installing Bouncer Desktop on Windows 11", and its certificate step is "Trust S6 Studios' certificate (once per PC)". The file name and steps are unchanged.
  • Internal Android test builds only: the feedback screen (#295). On Android 15 and 16, the shake-to-report screen's Send button no longer sits under the status bar. Its notice now says that a screenshot of the previous screen is attached, that what you type is included, and that credential values aren't captured.

Changes in the server

  • require_hardware_key needs verified evidence (#282). In 0.5.7, any key labelled as a biometric hardware key (platform-hw-uv) met this setting, so a device declaring an iPhone or a Mac met it on its word alone. From 0.5.8, a key meets it only with verified evidence for that key, from Android key attestation or a Windows TPM attestation, plus a check that it's you each time the key is used. The same rule applies when a resource's own key settings protect viewing, saving and version changes.
  • Each device records its verified evidence. The server keeps key_proof for each device: verified, unverified, unsupported or failed, with the kind of evidence (android-key, tpm or other). Migration 0020 adds it, and fills it in only from attestation records the earlier server verified for that same key.
  • A new opt-in, pairing.require_verified_approval_keys. It's off by default. See The opt-in.
  • A revoked device is told at once (#298). A device that's revoked while it's waiting for new events now gets the "removed" answer straight away, instead of after its wait times out.
  • No closure pushes to iPhones (#287). When a request ends, your server no longer sends iPhones the push meant to close its alert, because the iPhone app can't act on it in the background. The app removes the alert when you next open Bouncer. Android closure pushes still try for an hour, so a phone that comes back online within the hour can still remove a stale alert.

For operators

Who is affected

This only matters if a resource sets require_hardware_key: true, either on the resource itself or in defaults. If none does, approvals work as before. Skip to Upgrade order.

If one does, after the upgrade only two kinds of key can approve it:

  • an Android biometric key whose key attestation the server verified;
  • a Windows Hello key whose TPM evidence the server verified. No real PC has passed this check yet.

So these keys stop meeting it:

  • every iPhone and Mac key, because the server can't verify Apple key evidence. Pairing again doesn't change this;
  • Android biometric keys that paired without a verified attestation chain.

Windows Hello keys without verified TPM evidence, including every key enrolled before 0.5.7, didn't meet it in 0.5.7 either. All these keys can still deny, and can still approve resources that don't set require_hardware_key. require_hardware_uv is unchanged: it still accepts the label a device declares, unless you turn on the opt-in below.

Before you upgrade, check who approves each resource that sets require_hardware_key. If they all use iPhones or Macs, nobody will be able to approve that resource until one of them pairs a device with verified evidence, such as an Android phone that passes key attestation. Tell them before you upgrade.

After the upgrade, run bouncer-admin device list. KEY MEETS shows hardware_uv, hardware_key for a key that meets both settings, hardware_key (TPM attested) for a Windows Hello key with verified TPM evidence, hardware_uv (claim) for a biometric label without verified evidence, and neither otherwise. KEY PROOF shows the status and kind, for example verified/android-key or unverified/-. The JSON output (--json) has the full key_proof, including when it was checked.

An Android phone whose key isn't verified can sign out and pair again. If the phone's key attestation verifies this time, its new key meets the setting. Otherwise the person approves those resources on another device whose key is verified.

The opt-in: pairing.require_verified_approval_keys

It's off by default, and upgrading doesn't turn it on. When you set it to true, every approval key needs verified evidence, both when it's installed and every time it signs. Keys that are already paired are checked from the next reload.

With it on, a key without verified evidence can't sign anything, including denials and device settings. Every iPhone and Mac, and any Android phone or Windows PC whose KEY PROOF isn't verified, can then neither approve nor deny. Before you turn it on, run bouncer-admin device list and check KEY PROOF for every device people rely on.

People can still read status and sign a device out, and you can still pair and revoke devices. A Windows PC can still pair without a key and see requests, but its Windows Hello key needs verified TPM evidence when it's enrolled.

The server refuses a config that turns this on together with android_attestation: off. Turning it off again is logged as a policy loosening.

The refusal

A key that doesn't meet a requirement is refused with HTTP 422 assurance_not_accepted. The message says the key's evidence is unverified, unsupported or failed, and tells the person to enrol again with supported Android key or Windows TPM evidence, or to ask the operator. Changing a device's platform or key label doesn't create verified evidence.

Upgrade order

  1. If a resource sets require_hardware_key, check who approves it and tell them what changes (see Who is affected).
  2. If the server runs 0.5.6 or earlier, do the 0.5.7 steps first, including upgrading the role kit before you switch the server. 0.5.8 doesn't change the role kit.
  3. Take a database backup, and keep the current config and release files. You need all three to roll back.
  4. Upgrade the server, as in Upgrade and roll back. It applies migration 0020 when it starts.
  5. Run bouncer-admin device list from the same release, and check KEY PROOF and KEY MEETS for the people you told in step 1.
  6. Update other copies of the CLI, the MCP server and bouncer-admin, then the apps. Update the apps last: a 0.5.8 app connected to an older server offers only Deny on requests that need a hardware key.

Rollback

To go back to 0.5.7, restore the database backup you took before upgrading. A 0.5.7 server won't start on a database that has migration 0020, and editing or removing migration records to force it isn't safe. Anything that changed after the backup is lost. Before you start 0.5.7, take pairing.require_verified_approval_keys out of the config, because 0.5.7 won't start with it. Then follow Roll back, including resetting each SSH host's version state after the restore.

Known limits

  • #293 is open. Wider device checks aren't in this release: accepted platforms, minimum OS and app versions, Android's attestation revocation list and boot state.
  • #283 is open. A database restore or rollback can move the SSH revocation list's version below what hosts already hold, so each host needs the deliberate reset described in Upgrade and roll back.
  • #284 is postponed. There's no SSH gateway, session recording or gateway-enforced session cutoff.

What was checked

Each change has automated tests, run on fake data, Android emulators and a Windows test machine. On a real iPhone, from internal TestFlight, S6 Studios checked that the app reopens after a lock without a "can't reach" flash, that Notification settings opens the iOS page and returns to Bouncer, and that Privacy policy and Support open in Safari. Nothing else in 0.5.8 has been checked on a real phone or PC yet. These checks are still to do:

  • on a real Android phone: the reconnecting window, and alerts for ended requests being withdrawn (#289);
  • closure pushes on real phones, including the iPhone removing an ended request's alert when it's opened (#287);
  • on a real PC: the tray and taskbar checks, and a Windows Hello key passing the TPM check, which no real PC has done yet;
  • sending a real report from the internal Android build's feedback screen (#295);
  • upgrading a staging server with real data through migration 0020, and rolling it back to 0.5.7 by restoring the backup.

Versions

ComponentVersion
Server, Linux and Windows CLI, admin and MCP0.5.8+35
AndroidversionName 0.5.8, versionCode 35; internal versionName 0.5.8-internal
iOSshort version 0.5.8, build 35
Windows apptest-signed MSIX 0.5.35.0, internal MSIX 0.5.35.1, Microsoft Store package 1.0.35.0

This manual covers Bouncer 0.5.9. Built from source commit d8dfc7cd3265fd3a7cb58f78cbceb1ed6840d488 (workspace version 0.5.9+36).