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

How Bouncer protects access

This section explains what Bouncer does to protect secrets, what it relies on, and where its protection stops. Known limits lists the limits in one place.

How it works

OpenBao stores the secret values. Bouncer's own database stores information about secrets, requesters and devices, and the record of every request and decision, but not the values. The Bouncer server does handle secret values in plain text when a device views or saves a secret, and when someone creates a personal credential. So the server's own OpenBao login can read, at any time, every secret that's enabled for viewing in the app and every personal credential, and can write where it's configured to. For a request that needs approval, a person signs the decision on a paired device, and the requester can then fetch short-lived OpenBao tokens until the grant ends. Two experimental features can give access without a new approval: existing standing grants, and personal credentials set to Always approved (Approvals and access duration).

What protects what

ProtectionWhat it doesWhere it's enforced
Signed approvalsOnly a signature from a paired device's approval key approves. A requester key or device token can never approveThe server checks every signature, challenge and policy rule in one transaction
Exact scopeThe signature covers a hash of exactly what was asked: the resource, the requester, the duration and the reason. An approval can't be moved to another requestThe device recomputes the hash and refuses to sign if it differs; the server checks it again
Short tokensEach OpenBao token lasts minutes (5 by default), can read only that resource's paths, and never outlives its grantOpenBao, through the role kit's policies and token roles
Scoped OpenBao authorityThe role can issue and revoke tokens, read paths enabled for viewing, and read and write personal credential namespaces. It can write configured save paths. OpenBao does not check Bouncer's approvalsOpenBao policies; the role kit's check.sh checks their scope
RevocationA revoke stops new tokens at once and asks OpenBao to revoke those already issued. SSH certificates use a revocation list each host must fetch. From 0.5.7, hosts can fetch it while OpenBao is down, once Bouncer has read the CA public key; in 0.5.6 and earlier they can't (issue #281; SSH revocation)The server, then OpenBao
Values and metadataPostgreSQL stores hashes of requester keys, device tokens and pairing codes, plus access metadata. Secret values are stored in OpenBao, and handled in server memory when a device views or saves a secret, and when someone creates a personal credentialThe server's storage and API paths; this is not end-to-end encryption against the server operator
Admin off the networkAdmin commands go over a local Unix socket, never the networkFile permissions on the server's machine

Pages in this section

This manual covers Bouncer 0.5.7. Built from source commit cdd3b5958d5be0b33e865b1b56b770f6bccffaf7 (workspace version 0.5.7+34).