Sesame v0.5.1

This version also carries everything listed under 0.5.0, which was never published.

Sync

• A device shows what another device changed as soon as Sync applies it. The
  Vault screen used to stay as it was until the vault was locked and unlocked.
• Two devices no longer write new versions in turns while nobody is editing.
  Sesame now records the vault as it stands after it applies a change from
  another device, so it no longer takes that change for an edit of its own.
  This also stops a false message that two devices changed the vault after a
  device takes the new vault key.
• A device that is waiting for the new vault key now says that it needs the
  key. It used to say that it could not reach Sesame Sync.
• Adding a device shows that a code is being made, instead of saying that
  pairing could not start.
• After the vault key changes, a device still shows the names of other devices
  that it had read before. Sesame keeps those names on the device. A name it
  never read still shows as a device.

Logins

• The new login form helps with what you already have. Typing a website fills
  the login name when you have not typed one, says if you already have logins
  for that site, offers the folder those logins are in, and lists tags you have
  used. Each offer is one click and nothing is filled in without it, apart from
  the name.
• The user name and email lists put values from the same site first, then the
  ones used on the most logins, then the most recent. The lists still hold at
  most eight values and are read only when you focus the field.

Quick access

• The quick access window no longer closes the moment focus slips away. It
  waits a little over a second for focus to come back, and up to eight seconds
  while the pointer is still over it, so a window manager that follows the
  pointer or a small mouse movement does not close it. It still closes once
  focus has really gone, so decrypted titles do not stay on screen unattended.
• A pointer that rests over the results no longer takes the selection from the
  keyboard, and the arrow keys scroll the selected result into view.

Consistency and feedback

• Escape and a click on the backdrop no longer close the Sync set up and
  conflict dialogs while they are working, which matches their disabled buttons.
• Errors in the backup check use the same style as every other form error. They
  had a style name that nothing defined.
• The change master password dialog uses one name for the password in its
  labels and its button, and the field hints use straight quotes.
• Exporting a backup with your master password now refreshes the recovery
  health afterwards, and the backup buttons are off while one is running.
• Cancelling a breach check that could not be cancelled says so, and quick
  access says when it could not copy or open an item.

Everyday use

• Ctrl+C copies the text you have selected. It copies the password of the open
  login only when no text is selected.
• Saving an edit to a login keeps your search and filters. A new login, or an
  edit that moves a login to another folder, still shows the login in its
  folder.
• Locking the vault clears the search and filters, so the next unlock starts
  from the whole vault.
• Search accepts several words in any order and ignores accents, so "work
  northwind" and "cafe" find "Café Northwind" in the Work folder.
• Escape inside an open list, such as the sort order, closes only the list and
  not the dialog around it. The list button now says its current value, and
  Settings lists the slash key that opens search.
• A notice stays on screen while the pointer or keyboard focus is on it.
• The reason the vault locked now shows on the unlock screen, where it used to
  disappear before anyone could read it.
• Opening a saved site that Sesame refuses to open now shows an error, and the
  login is not counted as used.

Browser

• Settings says when another Sesame on the same computer already serves the
  browser extension. The first Sesame to start keeps the connection, as it did
  before, and a later one now says why the extension does not reach it.

Settings

• The Sync part of the Connections tab is arranged as Sesame Sync, Devices and
  Vault key, and the Devices list now includes this device.
• A dialog that replaces another one, such as the login editor handing over to
  the delete confirmation, no longer fades the dimmed background out and back
  in.
• The Sync panel says when Sesame checks the minimum Sync version, instead of
  only saying that it has not.
• A dialog is now moved into place before it is shown, so its entrance plays
  once from where it ends up. A dialog that was created closed and opened later
  was never moved at all.

Early access build for Windows 10 and 11, x64.

This installer is not Authenticode signed, so SmartScreen will warn you.
That is expected on this channel and does not mean the download is unverified.
Every file here was built in public CI from tag v0.5.1 and signed
keylessly with Sigstore, binding it to this repository and that commit.

Verify it before running. The script needs every file on this release, so
fetch the whole set into an empty folder rather than picking files by hand:

gh release create --help >NUL 2>&1 || winget install GitHub.cli
gh release download v0.5.1 --repo usesesame/sesame-desktop
winget install sigstore.cosign

Cosign ships as cosign-windows-amd64.exe and may not land on PATH. The script
looks for a command named cosign, so if it cannot find one, put a copy beside
the installer and add it for this window only:

curl.exe -L -o cosign.exe https://github.com/sigstore/cosign/releases/latest/download/cosign-windows-amd64.exe
$env:Path = "$PWD;$env:Path"

Then, in that folder:

Unblock-File .\verify-sesame-release.ps1
.\verify-sesame-release.ps1 -Installer .\Sesame_0.5.1_x64-setup.exe -EvidenceDirectory .

Both parameters are required. A pass ends with the workflow-verified line.
Without Cosign the script stops rather than skipping the publisher check; add
-HashOnly to check the hash alone, which proves the file is intact but not
who published it.

SHA-256 of Sesame_0.5.1_x64-setup.exe
07bef877f865a0e15626ce48d9f30422ddaf15f8885d7758c66a8b6904080db1

Release set digest: 0337c382a87b0919f8002814f72d1eb1a71eb6a3092ec101df06006e1cae3363

Release set digest: a716a2a60fc86f78464c0dcc6a223934a997d5de57d6f07b00f872c9f9ccc27b

Update freshness

Signed statements that the update manifest is current. This release must stay a pre-release, because it would otherwise replace the latest release.

Sesame v0.4.3

Browser

• Browser fill works again from installed Linux builds. Release builds hid the
  app and the browser helper from each other, so the helper refused every
  connection. The helper now leaves its own executable readable so the app can
  check it, and it trusts the Sesame process of yours that owns the private
  socket. The app still hides its memory from other programs.
• The AppImage now sets up browser fill. It copies its browser helper to
  ~/.local/share/sesame/browser-host and registers that copy, and the app
  checks the copy by the contents of its executable.
• Sesame registers its browser helper for Helium as well as Chrome, Chromium
  and Edge on Linux.

Linux packaging

• The AppImage uses your system's GLib instead of bundling its own, so GLib
  security fixes reach it through normal system updates. It needs GLib 2.80
  or newer.
• The AppImage no longer bundles the GnuTLS and proxy modules from
  glib-networking, which nothing in Sesame used.

Settings

• The Connections tab shows the server connection once instead of twice.

Early access build for Windows 10 and 11, x64.

This installer is not Authenticode signed, so SmartScreen will warn you.
That is expected on this channel and does not mean the download is unverified.
Every file here was built in public CI from tag v0.4.3 and signed
keylessly with Sigstore, binding it to this repository and that commit.

Verify it before running. The script needs every file on this release, so
fetch the whole set into an empty folder rather than picking files by hand:

gh release create --help >NUL 2>&1 || winget install GitHub.cli
gh release download v0.4.3 --repo usesesame/sesame-desktop
winget install sigstore.cosign

Cosign ships as cosign-windows-amd64.exe and may not land on PATH. The script
looks for a command named cosign, so if it cannot find one, put a copy beside
the installer and add it for this window only:

curl.exe -L -o cosign.exe https://github.com/sigstore/cosign/releases/latest/download/cosign-windows-amd64.exe
$env:Path = "$PWD;$env:Path"

Then, in that folder:

Unblock-File .\verify-sesame-release.ps1
.\verify-sesame-release.ps1 -Installer .\Sesame_0.4.3_x64-setup.exe -EvidenceDirectory .

Both parameters are required. A pass ends with the workflow-verified line.
Without Cosign the script stops rather than skipping the publisher check; add
-HashOnly to check the hash alone, which proves the file is intact but not
who published it.

SHA-256 of Sesame_0.4.3_x64-setup.exe
451717ba945ab42d9a4867541a78ea9e5548f1e843f05c85f4a61ea26fa55331

Release set digest: 74071e7e2a26ecba4218d7d672411ab1c3b3859247f5500a8ff5ab03ecba9167

Early access build for Linux x86_64: deb, rpm, and AppImage packages.

The packages are not signed by a distribution key. Every file was built in
public CI from tag v0.4.3 and signed keylessly with Sigstore.

SHA-256 digests are in SHA256SUMS-linux.

Release set digest: 53bd2a91c6435c435baa8364f5f19acdd63ae45260f1091abf9d5bcb45e950e9

Sesame v0.4.1

Sync

• Sync is off until you turn it on. When you do, your vault syncs between your
  devices through a server you run. A new device joins with a one-time code
  from a device that already syncs, edits sync on their own, and the vault bar
  shows the sync status. A join that was interrupted resumes with its saved
  approval.
• A desktop notices when a server offers an older copy than the one it already
  applied, or a second history that does not match its own. The setup screen
  explains the backup you need if every approved device is lost.
• Sync has not had an independent security review, and the hosted Sesame
  service does not offer it yet.

Your own server

• Settings can pair the desktop with a server you run. Sesame shows the
  server's key fingerprint before it sends any code, and it refuses the server
  later if that key changes.
• Pairing checks the device key store before it redeems a code.

Lock and release

• Quick access asks for your master password before it copies a login or
  Wi-Fi password, a card number or security code, a licence key, or an SSH
  private key, and the copy runs in native code. When the check is missing it
  points you to Sesame, and one check covers the next two minutes. Usernames,
  expiry dates, public keys and one-time codes still copy without it.
• Card numbers and security codes, Wi-Fi passwords, SSH private keys and
  passphrases, licence keys, document numbers, secret custom fields, secret
  legacy values and login backup codes stay in Sesame's native code when you
  open an item. Showing or copying one asks for your master password. Copying
  a login password, backup codes or any of these runs in native code, so the
  value never passes through the window, and neither does the login breach
  check. The editors open with those fields blank and keep the saved value
  unless you type a new one or choose Remove it, so editing an item no longer
  needs the master password. Login one-time codes, secure note contents and
  notes still show without the check.
• The vault locks on every check that reports a locked screen, not only when
  the screen first locks, so a vault unlocked or started behind a locked
  screen closes. On Linux, Sesame looks for missing screen lock and idle
  sources again every 30 seconds, and locks once the automatic-lock delay has
  passed with every source silent after one had answered. Settings says so
  when the desktop reports no screen lock source.
• On Linux the diagnostics log records key_page_fallback when the system
  refuses to lock the vault key into memory and Sesame keeps it in wiped
  ordinary memory instead. A failed key store no longer skips wiping the copy
  Sesame was handed.

Security

• The merge dialog no longer receives the password, 2FA seed, notes and backup
  codes of every selected login. It learns whether each field is present and
  whether the values differ, shows one password at a time behind the master
  password check, and merges at most 16 logins at once.
• On Windows a copied secret stays out of clipboard history and out of Cloud
  Clipboard sync. Both windows stay out of screenshots, screen sharing and
  Recall, and Settings has a switch that allows capture for support sessions.
  The editors also ask the browser not to autofill card, identity and login
  fields.
• Both windows refuse to leave the app's own address and cannot open new
  windows, and the content security policy is stricter.
• On Linux the web view runs in the WebKit sandbox. Sesame refuses to run it
  when bubblewrap cannot start it, so the deb and rpm packages now depend on
  bubblewrap and xdg-dbus-proxy. The JavaScript JIT is off in the web view on
  both systems, and Linux release builds remove the WebKit automation and
  inspector variables before the window starts.
• A browser approval needs 750 milliseconds of focused time in the Sesame
  window, so a click that lands as the window takes focus cannot approve a
  fill. Auto-type rechecks the focused window before each group of eight
  characters.
• Replacing a recovery kit now rotates the vault key, so the old kit no longer
  opens later versions of the vault, and the dialog offers to delete local
  backups made before the change.
• The vault file is padded before it is encrypted, so its size no longer shows
  how long an edit was.
• An update download is checked against the signed size, a stalled download is
  stopped, and redirects only go to the release hosts. The vault locks after
  the download passes its checks.
• The connection between the browser helper and the desktop reads each message
  under a time limit and keeps its folder private from the first moment. The
  diagnostics log is created private and refuses symbolic links.
• Two unused dependencies are gone, the updater plugin's zip support and the
  clipboard plugin, which removes three advisories in the zip crate.

Browser integration

• The desktop trusts the Chrome Web Store version of the extension as well as
  the side-loaded one. Update the desktop app before you install the store
  version, or it cannot connect.

Linux packaging

• The AppImage bundles Ubuntu 24.04 libraries, and OSV lists open advisories for
  twenty-eight of them, mostly in libsoup3, webkit2gtk and cups, with no fixed
  version for 24.04. The release gate records each one with its reason. The deb
  and rpm packages use your distribution's own libraries, so they get its
  fixes. Prefer them if your distribution has one.

Import

• The import preview counts every code or item in the file and says why each
  one that was left out was not added, such as HOTP codes, Steam Guard codes,
  unknown hash algorithms and rows with no name, username or password. It
  tells you to keep your old authenticator or password manager until you have
  moved those across.
• Bitwarden CSV files keep every website address in a cell that lists several.
  The import chooser now recommends Bitwarden JSON, which also keeps custom
  fields, secure notes, cards, identities and SSH keys.

Speed and setup

• Searching a large vault is faster. A search that matches every record takes
  about a fifth of the time at 10,000 records.
• The last setup screen offers to import your passwords, add a login and make
  a backup with a restore check.

Early access build for Linux x86_64: deb, rpm, and AppImage packages.

The packages are not signed by a distribution key. Every file was built in
public CI from tag v0.4.1 and signed keylessly with Sigstore.

SHA-256 digests are in SHA256SUMS-linux.

Release set digest: a5bab7eab2585e3d5ab80165141cdc7fc821fe80d24aa5e8f0e5b885804a34cc

Release set digest: 4a03ceebdb2090d999865e9d63472e8f9cb2373e2699805fe4c83ea8cbdd90af

Sesame v0.3.0

Unlock

• A PIN can have 6 to 12 digits and shows as one field with a dot per digit.
  Repeated digits and runs in order are refused. Existing 6-digit PINs still
  unlock.
• A new master password needs 12 characters and must pass the strength
  checks. Passwords are compared in Unicode normalized form, and existing
  vaults open unchanged.
• Changing the master password needs the current password and then the
  recovery kit. A forgotten password can be reset with the recovery kit.
• If you know the master password but lost the recovery kit, you can request
  a new kit. It is ready after 72 hours, measured with the time from
  usesesame.app and github.com, and a warning shows on every unlock until then.
• The vault locks on wake when the computer slept longer than the auto-lock
  delay.
• On Linux the device key is created only when you set a PIN, link an
  account, or enroll a device.

Security checkup

• The checkup finds breached passwords and expiring cards, and lists sites
  that offer two-factor or passkey sign-in. Breach checks send only the first
  five characters of a password hash.
• Each finding opens its login, and Change on site opens the saved website.

Account

• Account linking works on Linux when a Secret Service wallet is available.
• A tagged release fails before the build when the account capability public
  key is missing or malformed.

Browser integration

• Every fill of a matched login asks for approval. The 15-minute remembered
  approval is gone.
• The extension explains why a login matches and can fill one-time codes after
  a fresh approval. A fill on a lookalike website is refused.
• Old extension protocol versions are refused, and the extension no longer
  learns whether the vault is locked before you approve. Update the extension
  together with the desktop app.
• The browser connection works on Linux from the deb and rpm packages, and the
  release gate tests it against the live desktop.

Linux packaging

• The AppImage no longer bundles the Wayland client and cursor libraries, so
  its window no longer stays blank on newer Wayland hosts.
• The AppImage file name no longer stops the Windows publish step.

Vault and backups

• Restoring a backup over an existing vault needs it unlocked and your master
  password, and a backup from a different vault is refused.
• Changing the master password tries to remove the local backups and says
  when any remain.
• Readable exports keep values exactly as saved, warn about values a
  spreadsheet could run as formulas, and are written as private files.
  Partial exports name what was left out.
• Imports are bounded while they are read. SSH-only Bitwarden exports are
  accepted.
• On Linux Sesame flushes the vault folder after each save.
• Backup compatibility is shown before a restore starts.

Security

• Revealed passwords are not cached in the window. The clipboard timer runs in
  native code, and locking clears a secret Sesame copied.
• Saved items and decrypted buffers are wiped from memory when dropped.
• Files are chosen through the system dialog, so the window cannot name a
  file path.
• Vaults with key derivation settings below the minimum are refused.
• Website icons are fetched only after you turn them on. The breach check
  follows the system proxy.
• Update manifests must be signed, the window cannot use the updater plugin
  directly, and release builds no longer hold the signing keys.

Interface

• One type scale, measurable contrast for fields and quiet text, and one
  control style.
• Vault search ranks results, tolerates small typos, and has keyboard
  shortcuts and bulk actions.
• The vault list can copy a password without showing it.
• Status screens, empty states and the browser approval prompt are easier to
  read. Selection checkboxes sit centered on their rows.
• Fixes for modal teardown, duplicate tags, fields and URLs, async results
  landing on the wrong item, and needless repaints.

Diagnostics and release pipeline

• Dependency installs are locked and checked against the lockfiles, and
  release evidence records dependency hashes.
• The vendored GLib patch and every Linux package format are checked in CI.
• Card-fill and quick-access diagnostic codes are recorded instead of dropped.
• The build uses the TypeScript 7 native compiler.

Early access build for Windows 10 and 11, x64.

This installer is not Authenticode signed, so SmartScreen will warn you.
That is expected on this channel and does not mean the download is unverified.
Every file here was built in public CI from tag v0.3.0 and signed
keylessly with Sigstore, binding it to this repository and that commit.

Verify it before running. The script needs every file on this release, so
fetch the whole set into an empty folder rather than picking files by hand:

gh release create --help >NUL 2>&1 || winget install GitHub.cli
gh release download v0.3.0 --repo usesesame/sesame-desktop
winget install sigstore.cosign

Cosign ships as cosign-windows-amd64.exe and may not land on PATH. The script
looks for a command named cosign, so if it cannot find one, put a copy beside
the installer and add it for this window only:

curl.exe -L -o cosign.exe https://github.com/sigstore/cosign/releases/latest/download/cosign-windows-amd64.exe
$env:Path = "$PWD;$env:Path"

Then, in that folder:

Unblock-File .\verify-sesame-release.ps1
.\verify-sesame-release.ps1 -Installer .\Sesame_0.3.0_x64-setup.exe -EvidenceDirectory .

Both parameters are required. A pass ends with the workflow-verified line.
Without Cosign the script stops rather than skipping the publisher check; add
-HashOnly to check the hash alone, which proves the file is intact but not
who published it.

SHA-256 of Sesame_0.3.0_x64-setup.exe
90d76f3acbfe65415c355478bf4c3e1ae6682d668aee30e4d010ce94abec6f52

Release set digest: 50dde7084e7095216c70f6d54d4edd9880e42e014a39b032c82255abde1c4c1b

Release set digest: 90f6a71d459e9ad6505a9e0a33488dcde1b8adaed380bc4d3c410048525296f9

Sesame v0.2.5

Security

• On Linux the unlocked vault key is now held in memory the kernel has locked
  against swap, and Sesame wipes and releases that page when it locks,
  restores, or exits. If the kernel refuses the memory advice that keeps the
  key out of crash dumps and forked children, Sesame wipes the key and falls
  back to wiped-after-use memory instead of keeping it unlocked, and the copy
  made for that fallback is wiped the moment it is created.
• Vault files are safer to open and save. Opening never truncates a file that
  is already there, saving writes a staged file that is validated and swapped
  in by rename, and a link planted into the vault file's path is removed
  rather than written through.
• A save that would push the vault above its 64 MiB storage limit is refused
  with a message that says the saved vault has not changed.
• Replies to the browser extension must fit the message frame the host
  writes, and request buffers are wiped after use, so an oversized reply is
  refused and request bytes do not linger in memory.
• The parsers that read untrusted bytes, the native browser protocol and the
  sync envelope, run under seeded mutation tests: flipped bits, truncated
  payloads, spliced injections, and type-swapped fields must fail validation
  instead of panicking.
• Every Rust dependency is admitted by name:
  src-tauri/dependency-admission.json records each crate in the build and why
  it is needed, and the gate fails the build when an unlisted crate appears.
• rustls is updated to 0.23.45 for RUSTSEC-2026-0285, and the locked build and
  development dependencies are refreshed.

Interface

• The interface carries its design language end to end. Sesame now
  self-hosts the display, interface, and code fonts, Fraunces, Schibsted
  Grotesk, and Spline Sans Mono, and applies the refreshed tokens across the
  shell, menus, and views. The entry context menu handles every item kind,
  modals open at the app root so a view container cannot trap their backdrop,
  and the copy is shorter while stating the same facts.

Update and release pipeline

• The update chain binds the updater receipt to the exact installer. The
  manifest carries the download URL at the top level, and publishing refuses
  to continue when the manifest's URL, SHA-256, or byte count differs from
  the verified candidate.
• Publishing a release is resumable. If a publish is interrupted, the next
  run reconciles what is already public against the verified release set and
  uploads only what is missing, and a leftover asset is tolerated only when
  it matches this release's version.
• A release cannot publish until the packaged app opens every supported
  historical backup, restores it, restarts, and backs up again on both
  Windows and Linux. That restore evidence is produced by the release
  workflow and attached to the release.
• Linux packages ship from the same public release pipeline as the Windows
  installer: deb, rpm, and AppImage builds, each installed, launched, and
  uninstalled in the release gate before publication, and both platform
  lanes publish one shared release instead of two.

Early access build for Linux x86_64: deb, rpm, and AppImage packages.

The packages are not signed by a distribution key. Every file was built in
public CI from tag v0.2.5 and signed keylessly with Sigstore.

SHA-256 digests are in SHA256SUMS-linux.

Release set digest: 5197f6ef2892276aa8c638c5a36f885d0fbbfca7f1b22fcd651664dccd284133

Release set digest: d03977ef6c671c8d03f80a232e435d82260640f95f948de5f217fbaf56db6afa

Early access build for Windows 10 and 11, x64.

This installer is not Authenticode signed, so SmartScreen will warn you.
That is expected on this channel and does not mean the download is unverified.
Every file here was built in public CI from tag v0.2.5 and signed
keylessly with Sigstore, binding it to this repository and that commit.

SHA-256 of Sesame_0.2.5_x64-setup.exe
a1e0e90c29eb4d3cb9513d242965fa28e1754d60711ea3b51ab5e79d91105aae

Sesame v0.2.4

• Updating from 0.1.1 through 0.2.2 to 0.2.3 failed with a receipt mismatch:
  the 0.2.3 update receipt used a format those versions cannot verify. The
  update manifest again carries the receipt format every released client
  verifies, and the updater accepts both formats from this release on. Update
  to 0.2.4 from any earlier release; an install already on 0.2.3 updates
  manually once.

Early access build for Windows 10 and 11, x64.

This installer is not Authenticode signed, so SmartScreen will warn you.
That is expected on this channel and does not mean the download is unverified.
Every file here was built in public CI from tag v0.2.4 and signed
keylessly with Sigstore, binding it to this repository and that commit.

Verify it before running. The script needs every file on this release, so
fetch the whole set into an empty folder rather than picking files by hand:

gh release create --help >NUL 2>&1 || winget install GitHub.cli
gh release download v0.2.4 --repo usesesame/sesame-desktop
winget install sigstore.cosign

Cosign ships as cosign-windows-amd64.exe and may not land on PATH. The script
looks for a command named cosign, so if it cannot find one, put a copy beside
the installer and add it for this window only:

curl.exe -L -o cosign.exe https://github.com/sigstore/cosign/releases/latest/download/cosign-windows-amd64.exe
$env:Path = "$PWD;$env:Path"

Then, in that folder:

Unblock-File .\verify-sesame-release.ps1
.\verify-sesame-release.ps1 -Installer .\Sesame_0.2.4_x64-setup.exe -EvidenceDirectory .

Both parameters are required. A pass ends with the workflow-verified line.
Without Cosign the script stops rather than skipping the publisher check; add
-HashOnly to check the hash alone, which proves the file is intact but not
who published it.

SHA-256 of Sesame_0.2.4_x64-setup.exe
4c44664eb780de287266bd5b5719cf7da2cb3a7d7c7984e01073ea9cab4fe3c3

Sesame v0.2.3

• Restoring a backup from an older Sesame release now upgrades it to the current
  format instead of installing it as it was written. Backups written by 0.1.0
  through 0.2.2 are covered, and the selected backup file is never modified.
• Restore makes a safety copy of your current vault and only replaces it at the
  last step. If any step fails, your vault and the backup are left as they were.
• Restore errors now say what went wrong: a wrong master password, a damaged
  file, or a vault that needs a newer Sesame.

Early access build for Windows 10 and 11, x64.

This installer is not Authenticode signed, so SmartScreen will warn you.
That is expected on this channel and does not mean the download is unverified.
Every file here was built in public CI from tag v0.2.3 and signed
keylessly with Sigstore, binding it to this repository and that commit.

Verify it before running. The script needs every file on this release, so
fetch the whole set into an empty folder rather than picking files by hand:

gh release create --help >NUL 2>&1 || winget install GitHub.cli
gh release download v0.2.3 --repo usesesame/sesame-desktop
winget install sigstore.cosign

Cosign ships as cosign-windows-amd64.exe and may not land on PATH. The script
looks for a command named cosign, so if it cannot find one, put a copy beside
the installer and add it for this window only:

curl.exe -L -o cosign.exe https://github.com/sigstore/cosign/releases/latest/download/cosign-windows-amd64.exe
$env:Path = "$PWD;$env:Path"

Then, in that folder:

Unblock-File .\verify-sesame-release.ps1
.\verify-sesame-release.ps1 -Installer .\Sesame_0.2.3_x64-setup.exe -EvidenceDirectory .

Both parameters are required. A pass ends with the workflow-verified line.
Without Cosign the script stops rather than skipping the publisher check; add
-HashOnly to check the hash alone, which proves the file is intact but not
who published it.

SHA-256 of Sesame_0.2.3_x64-setup.exe
5361fb00145c1c27edb1d15316df3157ed433e2e262221566a2f9aa90ba9ee81

Sesame v0.2.2

• The release chain carries Linux end to end. The desktop app reports its real
  operating system when it registers with the account service, the updater
  runs on Linux, and update receipts are verified against the running
  platform. The release pipeline accepts Linux candidates and writes
  linux-appimage updater manifest targets, the server ingests them, serves
  update checks for the asking platform, and answers per-platform
  latest-release lookups, and the admin release controls and the website's
  builds page show both channels.

Early access build for Windows 10 and 11, x64.

This installer is not Authenticode signed, so SmartScreen will warn you.
That is expected on this channel and does not mean the download is unverified.
Every file here was built in public CI from tag v0.2.2 and signed
keylessly with Sigstore, binding it to this repository and that commit.

Verify it before running. The script needs every file on this release, so
fetch the whole set into an empty folder rather than picking files by hand:

gh release create --help >NUL 2>&1 || winget install GitHub.cli
gh release download v0.2.2 --repo usesesame/sesame-desktop
winget install sigstore.cosign

Cosign ships as cosign-windows-amd64.exe and may not land on PATH. The script
looks for a command named cosign, so if it cannot find one, put a copy beside
the installer and add it for this window only:

curl.exe -L -o cosign.exe https://github.com/sigstore/cosign/releases/latest/download/cosign-windows-amd64.exe
$env:Path = "$PWD;$env:Path"

Then, in that folder:

Unblock-File .\verify-sesame-release.ps1
.\verify-sesame-release.ps1 -Installer .\Sesame_0.2.2_x64-setup.exe -EvidenceDirectory .

Both parameters are required. A pass ends with the workflow-verified line.
Without Cosign the script stops rather than skipping the publisher check; add
-HashOnly to check the hash alone, which proves the file is intact but not
who published it.

SHA-256 of Sesame_0.2.2_x64-setup.exe
fd91d0ed65f1e1ff346784666bcee3b414a1238419cb490ca6dc7addd3c32a22

Sesame v0.2.1

• Revealing a saved password now asks for the master password in a proper
  dialog instead of an unstyled inline row. The login editor can also show the
  saved password it edits, verified the same way as the vault detail view, and
  saving an untouched password field still keeps the stored one.
• Copy and reveal prompts no longer stack notifications: opening the master
  password dialog does not also raise a "Nothing to copy" notice, and a wrong
  master password reports its error once, inside the dialog that asked for it.

Early access build for Windows 10 and 11, x64.

This installer is not Authenticode signed, so SmartScreen will warn you.
That is expected on this channel and does not mean the download is unverified.
Every file here was built in public CI from tag v0.2.1 and signed
keylessly with Sigstore, binding it to this repository and that commit.

Verify it before running. The script needs every file on this release, so
fetch the whole set into an empty folder rather than picking files by hand:

gh release create --help >NUL 2>&1 || winget install GitHub.cli
gh release download v0.2.1 --repo usesesame/sesame-desktop
winget install sigstore.cosign

Cosign ships as cosign-windows-amd64.exe and may not land on PATH. The script
looks for a command named cosign, so if it cannot find one, put a copy beside
the installer and add it for this window only:

curl.exe -L -o cosign.exe https://github.com/sigstore/cosign/releases/latest/download/cosign-windows-amd64.exe
$env:Path = "$PWD;$env:Path"

Then, in that folder:

Unblock-File .\verify-sesame-release.ps1
.\verify-sesame-release.ps1 -Installer .\Sesame_0.2.1_x64-setup.exe -EvidenceDirectory .

Both parameters are required. A pass ends with the workflow-verified line.
Without Cosign the script stops rather than skipping the publisher check; add
-HashOnly to check the hash alone, which proves the file is intact but not
who published it.

SHA-256 of Sesame_0.2.1_x64-setup.exe
4e9cc735f0810e9f7462f6d7c5a9c35135fde77c89c8e11e5231115653a6d2d1