Update encryption library data sources to include support for boringcrypto #263
Conversation
This file contains 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
…rypto Signed-off-by: Dom Del Nano <ddelnano@pixielabs.ai>
✅ Deploy Preview for docs-px-dev ready!
To edit notification comments on pull requests, go to your Netlify site settings. |
|
@pixie-io/maintainers this is ready for review. |
vihangm
approved these changes
Jun 13, 2023
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.
Our Go tls tracing is flexible enough that it instruments Golang's standard crypto and boringcrypto implementations. We should document that this is supported since it was reported as a gap in our feature set (pixie-io/pixie#597).
Testing done