Repository navigation
feat(pass): resolve wildcard se:// references in run #666
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
Merged
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
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
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
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
[high / security] Non-deterministic secret selection when wildcard matches multiple secrets
The PR removes the
len(envs) > 1error guard and replaces it with "first match wins" — but neither thesecrets.Resolverinterface nor the productionresolverClient(inx/api/resolver/resolver.go) defines or enforces any ordering on the returned slice. The concrete RPC client returns envelopes in the order the daemon's wire response provides them, which can vary across runs, daemon versions, or backend ordering changes.Trigger: any
se://env var containing*or**where the pattern matches two or more secrets.Impact:
Why tests pass but production is unsafe:
MockResolver.GetSecretsinx/testhelper/testing.gosorts results alphabetically by ID before returning (line 105 viaslices.SortFunc). This makes the wildcard test deterministic but masks the production non-determinism, where no such sort is applied.Fix: sort the returned envelopes by ID before selecting index 0, and optionally warn when
len(envs) > 1so the caller is aware of the disambiguation: