fix: harden Discord webhook client - #14
Merged
Merged
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
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.
Summary
User-AgentheaderRoot cause and impact
When
notifiers.discord.urlwas used, transport errors contained the request URL but redaction only knew aboutnotifiers.discord.token. The resulting error was logged by the app and could expose the webhook credential. Resty also supplied its generic default user agent rather than the format required by Discord's HTTP API.This change treats both token and webhook URL as sensitive on every Discord error path and configures the required client identity.
Validation
go test ./...(610 tests)go vet ./...go test -race ./notifier/discord