root
a9308a3e89
Why: the point of a sync server is that two people can work at once. Picking a winner was all this one could do while it could not read a vault. What, end to end: - A vault is created at /web or with `keeporg vault -create`: the server builds an empty KDBX 4 file, encrypts it with the password from the form, and stores it as version 1. An existing database can adopt a stored key with `keeporg db -id <id> -store-password`, which is verified against the stored file before it is accepted. - A stale push to a `merge` vault is no longer refused. The server opens the stored version and the pushed one in memory, folds them together, and stores the re-encrypted result. Clients push as usual and pull what comes back. Any failure answers 409 merge_failed and the client keeps its copy aside, so a failed merge still loses nothing. - At rest: vault contents stay KDBX-encrypted as always. A merge vault's password is kept AES-256-GCM-wrapped under a master key that lives outside the data directory, bound to the vault id, never returned by the API. A stolen data directory is ciphertext; a stolen data directory plus the master key is not. The server runs without a master key and simply refuses to create or merge vaults. This moves the server inside the trust boundary for vaults it can merge, which is inherent to merging and is stated plainly in the README, the handover notes and the web form itself. Key-less strategies are unchanged and remain the default for a database created without a password. Proved: two clients editing the same version are merged rather than refused, the newer edit of one entry wins, a merge failure leaves the stored vault untouched, `merge` is refused without a stored key, the wrapped key never appears in state.json or the API, and the web interface rejects a form without its CSRF token, withholds its cookie over plain http, and only offers groups the user administers. Checked by hand against the real thing: a vault created in a browser, edited by keepassxc-cli on two sides from the same version, merged by the server, and both entries read back out with keepassxc-cli. make check, make test-race, android lint and both .deb builds are clean.
26 lines
1.2 KiB
Plaintext
26 lines
1.2 KiB
Plaintext
Package: keeporgd
|
|
Version: @VERSION@
|
|
Section: net
|
|
Priority: optional
|
|
Architecture: @ARCH@
|
|
Maintainer: tiredsysadmin <rcmd@garage.rcmd.space>
|
|
Homepage: https://garage.rcmd.space/keeporg
|
|
Depends: adduser
|
|
Description: KeePass database synchronization server
|
|
KeepOrg stores KDBX files as opaque versioned blobs and arbitrates concurrent
|
|
writes between clients. It hosts many databases, controls access through a
|
|
tree of user groups, and accepts registrations by invite link or OIDC.
|
|
.
|
|
When two clients save at once it can merge both edits in memory, following
|
|
KeePass's own synchronization rules, so neither is lost.
|
|
.
|
|
Merging requires the server to hold the vault's password, which it keeps
|
|
encrypted under a master key in /etc/keeporg/master.key, created on first
|
|
start. Back that file up separately from /var/lib/keeporg: whoever holds
|
|
both can read every merge vault. Databases on any other conflict strategy
|
|
keep their key off the server entirely.
|
|
.
|
|
The service runs as the keeporg user with its data in /var/lib/keeporg and
|
|
its configuration in /etc/keeporg/server.json. Terminate TLS in front of it
|
|
with nginx or caddy, or point tls_cert and tls_key at a certificate.
|