root
8bbb3179a1
Why: collaborative KeePass use needs one arbiter of "who wrote last" that never sees a master password, plus access control that follows an org chart. What: stdlib-only Go server. Metadata is a single JSON document with one writer and atomic commit; KDBX payloads are versioned blobs on disk. Access comes from a group tree where a grant on a group reaches every member below it. Login is password+TOTP, invite links, or OIDC through a browser-approved device flow. Pushes carry If-Match and are arbitrated by a per-database merge strategy (server-wins by default). Updates are pushed to clients over SSE. Proved: go test ./internal/... covers RFC 6238 vectors, ACL inheritance and isolation, store rollback, blob pruning, every push verdict, and an end-to-end HTTP pass over login, conflict, force, read-only grants, invite redemption, TOTP enrolment, device login and the event stream.
12 lines
126 B
Plaintext
12 lines
126 B
Plaintext
/build/
|
|
/dist/
|
|
*.kdbx
|
|
*.deb
|
|
*.dmg
|
|
*.apk
|
|
*.aab
|
|
/android/.gradle/
|
|
/android/build/
|
|
/android/app/build/
|
|
/android/local.properties
|