Repository navigation
fix(crypto): sign-in never replaces a published key; qc keys publish (0.16.1, qc 0.12.0) - #342
Merged
Merged
Conversation
…(0.16.1, qc 0.12.0) Anthony (qc TUI): "[Encrypted message - decryption failed]". Cause: on 2026-10-27 02:07 UTC a browser signed in as chovy with empty key storage. postQuantumEncryption.initialize() generated a fresh keypair, and keySyncService.autoSyncOnLogin saw "local key differs from database" and published it over the account key (behaviour added in 11ced5a for rotation). Every message sent after that was encrypted to a key only that one browser holds, so qc and every other device failed. No reset happened (the key backup from 10-06 is untouched, /api/keys/reset never called). qc 0.11.0 changed no crypto code. - needsKeySync syncs only when the account has NO published key. A different key is reported (publishedKeyStatus 'differs', 'qrypt:key-mismatch' event), never replaced. - EncryptionWarning: "This device has different keys from your account" with Restore my keys (first) or a confirmed "Use this device's keys". "Generate new keys" now publishes explicitly (it relied on the sign-in sync). - qc keys [publish]: check whether this terminal holds the account key, and put it back (confirm or --yes). The TUI mismatch notice points at it. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
ThreatCrush Security Scan17 finding(s) MEDIUM: 13 | LOW: 4
Snippets are redacted; ThreatCrush never prints matched credential material. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Anthony (qc TUI): "[Encrypted message - decryption failed]".
Cause: on 2026-10-27 02:07 UTC a browser signed in as chovy with empty key
storage. postQuantumEncryption.initialize() generated a fresh keypair, and
keySyncService.autoSyncOnLogin saw "local key differs from database" and
published it over the account key (behaviour added in 11ced5a for rotation).
Every message sent after that was encrypted to a key only that one browser
holds, so qc and every other device failed. No reset happened (the key backup
from 10-06 is untouched, /api/keys/reset never called). qc 0.11.0 changed no
crypto code.
key is reported (publishedKeyStatus 'differs', 'qrypt:key-mismatch' event),
never replaced.
Restore my keys (first) or a confirmed "Use this device's keys". "Generate new
keys" now publishes explicitly (it relied on the sign-in sync).
it back (confirm or --yes). The TUI mismatch notice points at it.
Tests: 132 files / 871 tests green locally; next build + build-qc pass.
🤖 Generated with Claude Code