fix: refresh Security Seed before replication

Reason:
- A client that remains open during a remote database rebuild can retain the previous Security Seed and upload documents encrypted with the wrong key.

Changes:
- Fetch the remote Security Seed at every replication preflight instead of reusing the process cache.
- Add a regression test and an unreleased change note for issue #1018.
This commit is contained in:
Ouyang Xingyuan
2026-07-14 18:15:40 +08:00
parent 056d89aa4d
commit 45657ba39c
3 changed files with 54 additions and 1 deletions
+4
View File
@@ -5,6 +5,10 @@ The head note of 0.25 is now in [updates_old.md](https://github.com/vrtmrz/obsid
## Unreleased
### Fixed
- Refresh the remote Security Seed before each replication, preventing a client that remained open during a remote database rebuild from uploading data encrypted with the previous seed (#1018).
## 0.25.81
14th July, 2026