fix: qualify Matrix crypto dependencies without store migration #155
No reviewers
Labels
No labels
blocked
bug
documentation
duplicate
enhancement
good first issue
help wanted
invalid
question
waiting-on-julian
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
jlxq0/matrix-mcp!155
Loading…
Reference in a new issue
No description provided.
Delete branch "fix/dependency-gates-20261029"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
The current Matrix dependency graph retains vulnerable crypto buffers through both direct HKDF and the SDK OAuth chain. This updates the full chain, including an immutable reviewed OAuth 5 compatibility fork, while retaining Matrix SDK 0.19.1, its features and encrypted-store format. RMCP and the matching OpenTelemetry family also move to fixed versions.
Independent Python/old-Rust/new-Rust vectors protect legacy/device/recovery key derivations and directory names. CI rejects any old second block-buffer copy or non-immutable OAuth fork source.
Validation: 376 unit + 6 integration tests on Rust 1.96; strict Clippy/fmt on 1.98; 4 dependency-gate tests; fresh RustSec/OSV report zero vulnerabilities and retain two informational unmaintained-package notices (anymap2, derivative), with no advisory suppressions. Independent exact-head review and Forge CI are required before merge. This source prerequisite does not publish or deploy an image; a separately qualified runtime/release follows.
OAuth prerequisite: jlxq0/oauth2-rs#1, reviewed merged revision 3e44f8f85863c65fbac7fce732b5918bc8d5c323. Source rollback is a scoped revert; no store migration or credential changes.