[release/7.0-staging] Fix exporting certificate keys on macOS 14.4. #99779
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
Apple changed the error code we get back from a failed data-key export. This caused us to not attempt to export the key using the legacy APIs and assume the key export failed. This change adds the additional error code returned from macOS 14.4.
|
Tagging subscribers to this area: @dotnet/area-system-security, @bartonjs, @vcsjones |
This was referenced Mar 14, 2024
bartonjs
approved these changes
Mar 18, 2024
|
Approved via email. |
bartonjs
added
Servicing-approved
|
All failures look to be known. |
bartonjs
merged commit b880b97
into
dotnet:release/7.0-staging
111 of 120 checks passed
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Backport of #99768 to release/7.0-staging
/cc @vcsjones @bartonjs
Customer Impact
Reported by customers in #99735. Apple made a changes in macOS 14.4 that prevented private keys from
X509Certificate2from exporting. This affected customers that used APIs to get the exported key from a certificate in the macOS keychain.Regression
Apple changed the error code returned by one of their APIs. The change caused our error handling logic to not handle a recoverable error and instead treat it as an uncaught error.
Testing
Unit tests were added to prevent the fix from regressing.
Risk
Low. The change only affects macOS specific code and adds another error code to an already existing error handling path. The fix simply ensures we take the same error handling path with the new error code, in addition to the old one.