Add more robust reporting to SecureTransport errors on macos #6848
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
|
Sorry for the delay here - I was looking back through old PRs and realized that I never actually published my comments. 😓 Many apologies. I went ahead and manually merged this, with a few stylistic updates. Thanks for the contribution! |
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.
This pull request ensures errors from
SecureTransporton macos are handled properly whenCFStringGetCStringPtrreturnsnull. This occurs when the string encoding conversion is not cheap/efficient.I am making this pull request after encountering a
SecureTransport error: (null); class=Net (12)while working on https://github.com/mitre/hipcheck. With these changes, I now get an error message from macos instead of(null).