Your vault stays on your computer

Sesame keeps your passwords in one encrypted file on your computer. Only the desktop app can open it, and only with your master password.

The short version

  • Your passwords stay on your computer. The Sesame website never receives your vault. Sync is off until you turn it on, and then it sends only encrypted data to a server you run. You do not need a Sesame website account.
  • Only you can open the vault. It opens with your master password or your recovery kit. We cannot open it, and we cannot reset your password for you.
  • Sensitive actions ask for your password again. Showing or copying a password, card number, security code, Wi-Fi password, SSH key, or licence key, and exporting your vault, a backup, or your recovery kit, all need your master password, even while the vault is unlocked.
  • The browser extension cannot fill on its own. It stores no passwords and waits for you to approve each fill in the desktop app.
  • You can check the code. Sesame is open source, and every download can be traced to the source code it was built from.

How the parts fit

Sesame has three parts. Only the desktop app reads your vault. You can create, unlock, import, back up, and restore it without an account or an internet connection.

Website and account serviceThey publish releases and run optional accounts, and they never receive your vault.

Your own serverIf you turn Sync on, it holds an encrypted copy of your vault that it cannot read.

Browser extensionIt stores no passwords and asks the app each time it fills one.

Sesame desktop app
Window This is what you see and click.

asks

Vault core It holds the key and decides what leaves the app.

reads and writes

Vault file It stays encrypted on your disk.

What happens if

Someone steals your laptop

The vault file is encrypted. To open it, a thief has to guess your master password, and Sesame makes every guess slow on purpose. A long master password is your best protection, so Sesame asks for at least 12 characters.

Someone uses your computer while you are away

By default the vault locks after five minutes without use, and when the computer wakes from a longer sleep. Some Linux desktops do not report idle time, so lock the vault yourself there.

Even while it is unlocked, showing or copying a password asks for your master password. After three wrong tries Sesame makes them wait, starting at five seconds and growing to five minutes.

A website tries to take a password

A web page cannot start a fill by itself. The desktop app shows you which site is asking and waits for your answer, and it refuses any site whose address imitates one you saved.

A server is broken into

The Sesame website never has your vault. A server you run for Sync holds only encrypted data it cannot read, and your desktops check signed history before they accept a change. If you made an account, the Sesame website holds your email, a password hash, your sessions, your licence records, your linked desktops, your passkeys, your support requests, and a record of security events, and none of that can open a vault.

Someone tampers with a download

Every installer is built in public on GitHub. Its Sigstore record names the exact source commit, and the releases page lists a checksum for every installer and package. The app installs an update only when it carries Sesame's signature.

You forget your master password

Use your recovery kit to set a new one. If you still know the password but lost the kit, you can ask for a new kit. It is ready after 72 hours, and every unlock warns you until then, so you can cancel a request you did not make.

If you lose both the password and the kit, nobody can open the vault, including us.

What Sesame cannot stop

No password manager can protect you from everything, and these are the limits we know about.

  • Malware running on your computer can read your screen, record your keys, and read the app's memory while the vault is unlocked.
  • Malware in your browser can pretend to be the extension, so the approval in the Sesame window is the last check before a fill.
  • A PIN is a shortcut for this computer rather than a second lock. Software running as you can try PINs against a copy of the vault file, and each extra digit makes the search ten times larger.
  • Changing your master password tries to remove the local backups and says which remain, but it does not change exports or system backups you made before the change.
  • Anyone who can write to the vault folder can put back an older copy of the vault. Sesame keeps a record on this computer of the newest vault it has opened and asks you to confirm before it uses an older one, but a program running as you can delete that record.
  • Whoever learns your master password or recovery kit can open any copy of your vault, so keep the kit offline.
  • One-time codes, login notes, and secure notes that you have not locked still show without a password check, because the window has to display them. A locked secure note keeps its text out of the window until the check passes, and a vault with a locked note does not open in an older Sesame.

Technical details

This part is for readers who want to check the design against the source code.

Encryption
XChaCha20-Poly1305
Master password to key
New vaults and a changed master password use Argon2id with 128 MiB of memory and 3 passes. Sesame still opens older vaults that use at least 64 MiB, and refuses files with weaker settings.
Opening a file
Sesame checks that a file is genuine before reading it, and refuses files that were tampered with, relabelled, or made by a newer version.
Saving
Sesame writes a new file, checks it, and then swaps it in, so a failed save leaves the old vault as it was.
Key in memory on Windows
The key stays out of the page file, and Sesame keeps it encrypted between uses.
Key in memory on Linux
Sesame asks the system to keep the key out of swap, crash dumps, and child processes. If the system refuses, Sesame keeps the key in ordinary memory that it wipes on lock and writes a note to the diagnostics log.
File size
Sesame pads the vault file before it encrypts it, so its size does not show how long an edit was.
Recovery kit
Replacing a recovery kit rotates the vault key, so the old kit no longer opens later versions of the vault.
Secret fields
Card numbers, security codes, Wi-Fi passwords, SSH keys, and licence keys stay in the app's native code, and copying one never passes it through the window.
Browser approval
An approval needs 750 milliseconds of focus in the Sesame window, so a click that lands as the window takes focus cannot approve a fill.
Window hardening
On Linux the web view runs in the WebKit sandbox, and Sesame refuses to run it when the sandbox cannot start. Both systems turn off the JavaScript JIT in the web view, and the windows cannot leave the app's own address.
Screen capture
On Windows, a copied secret stays out of clipboard history and Cloud Clipboard sync, and both windows stay out of screenshots, screen sharing, and Recall. A setting allows capture for support sessions.
Updates
Sesame checks an update download against its signed size, stops a stalled download, and follows redirects only to the release hosts.
Sync
Sync is off until you turn it on. Desktops check signed history before they accept changes, and a desktop warns you when a server offers an older copy or a second history that does not match.
Moving the vault key
When Sync gives your vault key to a device that has the newer key, it adds a post-quantum key exchange, ML-KEM-768 combined with X25519. Once any device in your vault has the newer key, Sesame refuses a new device that offers only the older key unless you allow it for that pairing. Changing the vault key shows the new recovery kit first and waits until you confirm that you saved it. Nobody independent has reviewed this exchange.
Breach check
Sesame sends only the first 5 characters of the password's SHA-1 hash to Have I Been Pwned.
Website icons
Icons stay off until you turn them on, because fetching an icon tells that site you saved it.

Not done yet

  • No independent reviewer has audited Sesame yet, so keep an encrypted backup and move over a few accounts at a time.
  • The browser extension is in the Chrome Web Store only, and the Firefox version is experimental.
  • The Windows installer is not Authenticode signed yet, so SmartScreen warns on first run.
  • Linux packages do not update themselves yet, so download new versions from the releases page.
  • Sync has not had an independent security review, and the hosted Sesame service does not offer it yet.
  • The post-quantum key exchange does not protect a vault key that was sent to a device before it had the newer key, and changing the vault key protects only what is written afterwards. Device signatures, the pairing code exchange, and the connection to your server are not post-quantum, and Sesame is not quantum safe.
  • The AppImage bundles Ubuntu 24.04 libraries that have open advisories with no fixed version yet, so prefer the deb or rpm package if your distribution has one.

Report a problem

If you find a security problem, report it privately with GitHub's Report a vulnerability form. Please do not open a public issue, and use made-up data in your report. The security policy says what to include and how fast we reply.

Every part of Sesame is open source under the GNU Affero General Public License v3.0 or later, so you can read the code behind every claim on this page.