Skip to content

Flowsta Vault v1.2.0

Latest

Choose a tag to compare

@github-actions github-actions released this 04 Aug 11:32
· 1 commit to main since this release

Flowsta Vault v1.2.0

Zero-knowledge desktop companion for Flowsta — holds your keys, your data, signs your files, never leaves your machine.

Fixed

  • Signing in on flowsta.com from Chrome and other Chromium browsers works
    again.
    The Vault was refusing to sign the website's login challenge; it
    now recognizes that challenge as first-party and signs it normally.
    Sign-in requests carrying other reserved content are still refused, and
    only Flowsta pages may ask.
  • Profile edits approved from the web update your public page. A
    name or picture change made on the dashboard and approved in the Vault
    updated the Vault itself but could leave your public profile page
    showing the old name until your next in-app edit.
  • The plan status in the header menu loads on demand when the Vault
    started without a connection.
  • Revocation marks stay visible after a reset or restore. Setting a
    vault up again on a machine that had one before could quietly revert part
    of the signing engine, which hid revocations from your records view. The
    Vault now brings the signing engine current every time it starts.

Added

  • After restoring your identity, the Vault asks before apps can write.
    The dashboard offers "import your export" or "start fresh"; until you
    choose, connected apps cannot overwrite or delete backup slots your
    export may be about to fill. A completed import answers the question
    automatically.
  • Backup answers apps can trust. Retrieving a backup now tells the
    requesting app whether the slot is empty, holds another identity's data,
    or exists but cannot be read - three different answers instead of one
    "not found". Apps use this to avoid ever treating someone else's slot as
    their own.
  • Every response names the identity that answered. Bridge responses
    carry the Vault's identity while unlocked, and an app can pin any request
    to the identity it expects - the Vault refuses the call if it holds a
    different one, even while locked.
  • A connected app can disconnect itself. Apps may revoke their own
    identity link through the bridge; disconnecting in the Vault remains
    unchanged.

Changed

  • After a phrase restore, setup hands you straight to the recovery
    question.
    The final screen now explains that the dashboard will ask
    whether to import your export or start fresh, instead of describing
    menu steps to find on your own.
  • Imports report what actually happened. Importing an export preserves
    each record's original timestamp, counts unreadable and unsupported
    records instead of skipping them silently, and finding nothing new to
    restore is explained plainly rather than shown as a success. Replacing
    existing records is an explicit choice, never the default.

Downloads

See assets below for platform-specific installers.