Add xcprivacy handling for modules that link OpenSSL. #285
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
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.
Fixes #268.
Fixes #286
As of April 2025, Apple has started flagging certain third-party SDKs as "privacy sensitive". OpenSSL is one of the affected libraries; this PR adds an
.xcprivacyfile for the two Python modules that link OpenSSL (_hashliband_ssl). The Xcode project can then post-process these.xcprivacyfiles into the final Framework.Also performs post-processing to extract dSYM files into the right location in the built project.
Currently submitted as a draft awaiting confirmation that this actually satisfies Apple's review requirements. An app using these files has passed initial automated validation and reviews.
PR Checklist: