feat(audit): fail closed without signing secret - #76
Open
P4ST4S wants to merge 1 commit into
Open
Conversation
|
Codecov Report❌ Patch coverage is
📢 Thoughts on this report? Let us know! |
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
Make audit signing fail closed: when
audit.signis enabled, configuration loading now requires a non-blank signing secret before any store, listener, dashboard, metrics server, or upstream process is initialized.Introduce
MCP_AUDIT_SIGNING_SECRETas the preferred environment variable while preservingAUDIT_SECRETcompatibility.Context
Closes #67.
Stacked on #75 and #74.
Approach
MCP_AUDIT_SIGNING_SECRET, then legacyAUDIT_SECRET, thenaudit.secretsign=falsebehavior without requiring any secretTest plan
go test -race ./cmd/mcp-audit ./internal/audit/... ./internal/proxy/...go test -race ./...go build ./...go vet ./...audit signing is enabled but no signing secret is configuredAll automated commands pass and the negative startup check returns the expected configuration failure.
Stability impact
This intentionally changes the existing
audit.sign: truemisconfiguration from silently unsigned output to a startup failure.audit.sign: falseremains unchanged.The new environment variable is additive. The existing
AUDIT_SECRETenvironment variable andaudit.secretconfig key remain supported.Notes for reviewer
Minimum secret length is warning-only in v1.2.0 to avoid rejecting existing non-empty secrets. Missing and whitespace-only values are hard failures.