SecretSpace Sync Server for Linux 2.0.0-alpha.3 (test version)

SecretSpace Sync Server 2.0.0-alpha.3: a test version for SecretSpace 3. For your 2.x vaults, the release marked Latest is all you need.

What's new

• Sharing a vault between accounts, for the test clients Windows 3.0.0-alpha.6 and Linux 1.0.0-alpha.6:
  • a vault can have several members, each an owner, an editor or a reader;
  • the server refuses a reader's upload;
  • a member can leave a vault; a vault always keeps at least one owner.
• Removing a member changes the vault's key. The owner's device sends the vault under a new key in one call; the earlier revisions (under the old key) are dropped, and an upload still made under the old key is refused.
• What the server never sees: a vault's key. A new member's copy arrives wrapped to their public key by the owner's device.
• A log.
  • _v2/vaults/<id>/audit.log for each vault: uploads, members added or removed, key changes. The vault's owners can read it in the app.
  • _v2/logins.log: logins, failed logins, accounts made, password changes. Read it on the server.
  • It holds no vault content, keys or names, and nothing about who viewed or copied an entry. Files rotate at 2 MB.
• /health now lists "features": ["vaults", "sharing"].
• An account whose name contains a space can now log in.
• 2.x sync is unchanged: the /vault/<user> routes and the token work exactly as in 1.x.
• Accounts and vaults made with 2.0.0-alpha.1 or alpha.2 keep working.
• The API is described in the README under API v2.

Install

Same as the release marked Latest (README). It runs on the same store, token and settings, so you can go back to the Latest release by reinstalling it. Accounts made with this test version then just aren't served.

SHA-256 checksums are in SHA256SUMS.txt.

🤖 Generated with Claude Code