chore: Update triton-go dependency to avoid embedded RSA key #2380
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.
PR Description
A concerned party discovered an RSA Private Key embedded in the Alloy 1.5.1 build. After some investigation, we discovered that this came from a test export in an indirect dependency which moved the key into its test code in a later release TritonDataCenter/triton-go#174. This PR updates the indirect dependency to avoid future security concerns, though this was not actually a real private key leak.