fix: Docker-readable QClaw/QwenWork tokens - #45
Merged
Conversation
Windows no longer writes DPAPI blobs into SQLite when MASTER_KEY is unset. New imports share the sidecar key file with Linux containers. Existing WorkBuddy Fernet rows are unchanged. Official QClaw/QwenWork login files remain Windows-only; import them on the host, then Docker reads the DB.
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
1 participant
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.
Scope
Linux Docker cannot decrypt official QClaw / QwenWork login files (Windows DPAPI). It also could not decrypt SQLite rows written on Windows as
enc:v1:dpapi:.CB_GATEWAY_MASTER_KEY)./authmount are unchanged../data.Verification
python -m pytest -q(157 passed)/healthshows workbuddy 3 + qclaw 1 + qwenwork 1; container can decrypt all tokens.