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

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

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

What's new

• Several vaults per account, for the test clients Windows 3.0.0-alpha.5 and Linux 1.0.0-alpha.5:
  • an account can have up to 50 vaults besides its personal one;
  • new calls to create, rename and delete a vault (POST /v2/vaults, PUT /v2/vaults/<id>/name, DELETE /v2/vaults/<id>);
  • only a vault's owner can rename or delete it.
• A deleted vault is moved, not erased: its folder goes to _v2/deleted/ inside the vault store.
• What the server never sees: a vault's key or its name. Both arrive encrypted.
• /health now lists "features": ["vaults"], so a client can tell an older 2.0 server apart.
• 2.x sync is unchanged: the /vault/<user> routes and the token work exactly as in 1.x.
• Accounts made with 2.0.0-alpha.1 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

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

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

What's new

• Accounts for SecretSpace 3 (API v2), for the test clients Windows 3.0.0-alpha.3 and Linux 1.0.0-alpha.3:
  • sign-up, with the server's token as the sign-up code;
  • login sessions (12 h);
  • a personal vault per account, with the same revision and conflict rules as 2.x.
• What the server never sees: a master password, a Secret Key or a vault key.
• 2.x sync is unchanged: the /vault/<user> routes and the token work exactly as in 1.x, so 2.x clients keep syncing with this server.
• Where account data lives: _v2/ inside the vault store, so a backup of the store includes it.
• 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

SecretSpace Sync Server for Linux 1.5.0

SecretSpace Sync Server for Linux 1.5.0.

What's new

• Renamed from PassMan to SecretSpace, in the names you read only. What a running server is made of keeps its name: the service passman-sync, the user passman, /opt/passman/server, /etc/passman, /var/lib/passman/store, and the sync protocol. An existing server needs no change.
• The systemd unit and LICENSE now always have Linux line endings. 1.4.2's tarball had Windows ones.
• Licence: GPL-3.0-only (was MIT), and a SECURITY.md.

The server itself behaves exactly as 1.4.2. Upgrading is optional.

Install

Download secretspace-server-linux-1.5.0.tar.gz and unpack it (tar -xzf secretspace-server-linux-1.5.0.tar.gz). It holds server/ (the server, the setup and the systemd unit), the README and the licence. Then follow Install on Ubuntu in the README from step 2, using the unpacked folder.

Upgrading: copy passman_server.py, passman_setup.py and version.py to /opt/passman/server/, then restart passman-sync (Updating in the README). Vaults, the token and sync.env are untouched.

SHA-256 checksums are in SHA256SUMS.txt.

🤖 Generated with Claude Code

PassMan Sync Server for Linux 1.4.2

PassMan Sync Server for Linux 1.4.2.

Install

Download passman-server-linux-1.4.2.tar.gz and unpack it (tar -xzf passman-server-linux-1.4.2.tar.gz). It holds server/ (the server, the setup and the systemd unit), the README and the licence. Then follow Install on Ubuntu in the README from step 2, using the unpacked folder in place of ~/PassMan-Server-Linux. Cloning the repository, as the README's step 1 does, gives you the same files.

Upgrading: copy passman_server.py and passman_setup.py to /opt/passman/server/ and restart passman-sync (Updating in the README). Vaults, the token and sync.env are untouched.

What's new

• 1.4.2: MIT licence added, and neutral example addresses in the setup help and README. The server itself is unchanged, so there is no need to upgrade from 1.4.1.

SHA-256 checksums are listed in SHA256SUMS.txt.

🤖 Generated with Claude Code

PassMan Sync Server for Linux 1.4.1

PassMan Sync Server for Linux 1.4.1.

Install

Download passman-server-linux-1.4.1.tar.gz and unpack it (tar -xzf passman-server-linux-1.4.1.tar.gz). It holds server/ (the server, the setup and the systemd unit) and the README. Then follow Install on Ubuntu in the README from step 2, using the unpacked folder in place of ~/PassMan-Server-Linux. Cloning the repository, as the README's step 1 does, gives you the same files.

Upgrading: copy passman_server.py and passman_setup.py to /opt/passman/server/ and restart passman-sync (Updating in the README). Vaults, the token and sync.env are untouched.

What's new

• 1.4.1: HTTP tests for the server (79). They found two small issues, now fixed: /vault/<user>/meta/<anything> returned the meta (now 404), and the access log kept query strings.
• 1.4.0: setup --allow-from lets extra addresses through the ufw rule.

SHA-256 checksums are listed in SHA256SUMS.txt.

🤖 Generated with Claude Code