Add support for fallback keys #1710

Merged
nex merged 3 commits from eve/ackduck:I1228 into main 2026-05-04 20:05:27 +00:00

3 commits

Author SHA1 Message Date
523939152f docs: Add changelog
All checks were successful
Checks / Changelog / Check changelog is added (pull_request_target) Successful in 32s
Documentation / Build and Deploy Documentation (pull_request) Has been skipped
Checks / Prek / Pre-commit & Formatting (pull_request) Successful in 1m18s
Checks / Prek / Check changed files (pull_request) Successful in 6s
Checks / Prek / Clippy and Cargo Tests (pull_request) Successful in 9m6s
2026-05-01 08:22:07 +00:00
f78398d5e5 feat: Add support for fallback keys
Fallback keys can be provided by client devices to be used in case the
supply of one-time keys run out. The server will store one fallback key
per user, per device, per algorithm. The server will keep track of
whether this fallback key has been used or not.

The  /keys/claim endpoint now provides a fallback key
if no one-time key is found

The /keys/upload endpoint now accepts fallback keys

The /sync endpoint now informs the client of the algorithms for which it
has an unused fallback key in stock.
2026-05-01 08:22:04 +00:00
0791a909e2 feat: Implement serialization/deserialization for booleans 2026-05-01 08:10:38 +00:00