Conversation
Resolve the connecting process with Security.framework before accepting the helper XPC connection. This avoids rejecting valid clients when NSRunningApplication does not provide a bundle identifier to the privileged helper. Add regression coverage for accepted and rejected client identifiers.
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
1 participant
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.
Summary
Why
When the helper runs as a privileged launch daemon,
NSRunningApplicationmay not provide the connecting application's bundle identifier. This rejects a valid ClashX Meta connection and can trigger repeated helper installation prompts on macOS Tahoe.The new validation resolves the live process through Security.framework and checks its signing identifier before accepting the connection.
Testing
Tests/HelperXPCSecurity/run.sh.Fixes #209