Manual for Bouncer 0.5.7. Chapters state version and distribution limits. Source cdd3b59, site build 20 November 2026. Your server or app may run an earlier version.
On this page
Bouncer 0.5.0
Every app shows 0.5.0+27 under Settings > About. On Android the version
code is 27. On Windows, the test-signed installer is package version
0.5.27.0. There was no GitLab release of 0.5.0. The first 0.5 release
published on GitLab is 0.5.4.
This release changes the server as well as the apps. The apps still work with a 0.3.8 server; they just don't show credential types until the server is upgraded.
For administrators
- Migration 0013 adds an optional credential type to personal credentials. The server applies it at start-up. Back up before upgrading.
- Upgrade the server before adding
credential_typetobouncer.yaml. Servers older than 0.5.0 refuse it: reload is refused and restart fails. - To roll back, remove
credential_typefrom the config, then restore your backup (Upgrades).
What's new for app users
Requests lead with the decision
A request now opens with who wants to do what to which credential, then the requester's reason (marked as not checked by Bouncer), then three short rows: who is asking, the requesting app exactly as the requester reported it, and the credential with a Read or Save · N fields label. One sentence says what approving does, and the time left to answer is shown apart from how long access would last.
- A read says how long access lasts. A save says it allows one update of N fields, that the saved changes stay after the sending window, and that it doesn't give read access.
- The clock counts down to the deadline for answering. With reduced motion turned on in your system settings it doesn't move, and it never flashes. Screen readers hear the time left by the minute, then at 30 and 10 seconds. Once time runs out, nothing can be approved or denied.
- More information, closed at first, holds the host, network address, app, key and field details.
- Inbox cards lead with a short title, such as "Save new values to Demo API key", and say "N left to answer".
- On Windows, the request pane says what approving gives, in the same words as the phone, and the footer reads "Approving signs with Windows Hello on this PC, and so does denying."
Credential types
A credential can say what kind it is (API key, password, certificate, SSH private key and so on), and the apps show a matching icon. The type only changes the icon; it doesn't change who can use the credential. The owner of a personal credential can choose its type in the app once the server supports it.
Clearer messages when an Android phone won't approve or deny
Before, the app said "Unlock it and try again" for every problem. Now it says which one it is: the check was cancelled, the phone is locked, there were too many attempts, the key needs pairing again, or Android needs a fresh unlock.
On Android 12 to 14, a phone unlocked by face (on many phones) or by Smart Lock doesn't count as unlocked for Bouncer's approval key. Lock the phone and unlock it with your PIN, pattern, password or fingerprint, then try again. The app now explains this as "Android needs a fresh unlock".
iPhone
When a request is decided, expires or is cancelled, the server now sends iPhones a silent update instead of a second alert. (The iPhone app wasn't released then.)
Windows fixes
- The install guide no longer says uninstalling removes the pairing. Sign out before you uninstall.
- Pairing again clears a confirmed "removed" notice.
- After you answer No to Windows' passkeys question, the message names both the passkeys setting and the Windows Hello PIN.
Known issues
- "Always" and "Always approved" are experimental, and their policy is not decided. Personal Always approved is off unless an administrator allows it. It has two open problems: a person's command-line key can get the value with no device, and the kill switch does not stop new Always approved uses. Default durations include Always unless disabled. Administrators: keep both off with
durations.always: falseandceilings.always_approved: false(Approvals and access duration). In the apps choose a time limit and Approval required. Check any standing grants with your administrator. - Some Android phones need a fresh unlock before they approve, as described above.
What was checked, and on what
- The new screens: automated widget and screenshot tests (phones at two widths, large text, light and dark, and the Windows pane), and the release checks of the installed test build on an Android emulator and a Windows test machine.
- Not yet checked on real phones and PCs: real fingerprint and Windows Hello prompts, TalkBack and Narrator reading the clock, and the system reduced-motion setting.
- The iPhone silent update: the server's tests only. No push had reached a real iPhone when this build was made.