Help / Devices & trust
Devices & trust
Updated July 15, 2026
Your password alone is not enough to get at your secrets from an unfamiliar machine. Each device identifies itself, and an unrecognised one has to be let in before it gets a session.
What you will see
If you sign in from a new machine, the login stops rather than completing:
$ bippass login Device pending approval — your workspace manager has been notified. Re-run 'bippass login' once approved.
There is no waiting or polling — approve the device from a machine you already trust, then run the command again. If instead you are told the device needs verification, check your email for the link and log in again afterwards.
How a device is recognised
The CLI derives a fingerprint from your hostname, OS and architecture plus a random identifier it stores at ~/.bippass/device_id. Delete that file and the machine looks new again, and will need approving.
Signing out
logout clears the stored token and your unlocked key from this machine. It does not touch other devices.
$ bippass logout