Use legacy OpenSSL Format for Apple Devices #14718
Merged
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.
Description
Uses legacy key format to generate
.p12
and.mobileprovision
files.Motivation and Context
openssl@3
uses a modern private key format unsupported on Apple devices because Apple has not updated its libraries. Importing generated.p12
files into the modern macOS and iOS keychain leads to the wrong password error. If you try to export a private key from.p12
and import it into Keychain separately, it will show the wrong format error.Closes #14558
Based on #14622 with applied comments.
How Has This Been Tested?
METHOD=local ENDPOINT=<ip_adderess> USERS=hello,world ./install.sh
. I had to modify the install script to point to the fork on thegetAlgo
step.mobileprovision
filesTypes of changes
Checklist: