Repository navigation
Several vaults per account (API v2, 2.0.0-alpha.2) - #11
Open
usermaneGermane wants to merge 1 commit into
Open
usermaneGermane wants to merge 1 commit into
usermaneGermane wants to merge 1 commit into
Conversation
An account can now hold further vaults besides its personal one: - POST /v2/vaults creates one, owned by the caller. The client makes the id and the key; the key arrives wrapped to the owner's public key and the name sealed under the vault key, so the server can read neither. - PUT /v2/vaults/<id>/name and DELETE /v2/vaults/<id>, owners only, never for the personal vault. A deleted vault's folder is moved to _v2/deleted/, not erased. - /v2/me lists every vault of the account; the blob routes work for the new vaults exactly as for the personal one. - At most 50 further vaults per account. - /health lists "features": ["vaults"], so a client can tell an older server apart. 2.x routes are unchanged. An account made by 2.0.0-alpha.1 needs no change. tests/test_server_v2_vaults.py: 44 tests; 9 of 9 deliberately broken servers were caught. Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_011ojnyVg7ccsR3pZ64s7aRH
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
Phase 3 of SecretSpace 3 on the server: an account can hold several vaults (2.0.0-alpha.2, a test version). It is also the groundwork for sharing a vault in phase 4: each vault has its own key, stored only wrapped to a member.
Changes
POST /v2/vaults: a further vault, owned by the caller. The key arrives wrapped to the owner's public key and the name sealed under the vault key, so the server can read neither.PUT /v2/vaults/<id>/nameandDELETE /v2/vaults/<id>: owners only, never for the personal vault. A deleted vault's folder is moved to_v2/deleted/, not erased./v2/melists every vault of the account. The blob routes (If-Match, 409, 428, PMV3 id check) work for the new vaults as for the personal one./healthadds"features": ["vaults"].Checked
tests/test_server_v2_vaults.py: 44 new tests over real HTTP; the full suite passes locally.server/passman_server.pyis byte-identical in SecretSpace-Server-Linux and SecretSpace-Server-Windows.The tests and README text were written by a Sonnet 5.5 subagent and reviewed.
🤖 Generated with Claude Code
https://claude.ai/code/session_011ojnyVg7ccsR3pZ64s7aRH