fix(tui): redact Telegram bot tokens in doctor reports#682
Open
9s5bz2jvd2-lang wants to merge 3 commits into
Open
fix(tui): redact Telegram bot tokens in doctor reports#6829s5bz2jvd2-lang wants to merge 3 commits into
9s5bz2jvd2-lang wants to merge 3 commits into
Conversation
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.
Summary
redaction.jsonThe rule is intentionally conservative: 6–12 decimal digits, a colon, and at least 30 ASCII characters from
[A-Za-z0-9_-]. It matches the existing LingTai kernel trajectory-redaction heuristic; it is a high-confidence redaction boundary, not a claim that 12 digits is Telegram's protocol maximum. The 13–16 digit cases are therefore locked as preserved near misses.Validation
go test ./internal/doctorreport -count=1go test ./internal/tui -count=1go test ./... -count=1go vet ./...git diff --check