Skip to content

Conversation

@steven-joruk
Copy link
Collaborator

This also adds built in support for client validation using audit tokens on macOS <= 11.x if the audit_token feature is enabled.

If users try to use client validation without the audit_token feature enabled on macOS <= 11.x then clients will silently be rejected. I've opened an issue to discuss adding logging.

I tested this on macOS 11 with the audit_token feature enabled and disabled, with and without code signing requirements enabled, and using clients that match and do not match the code signing requirements.

I'll add some tests soon, I'll think about the best way to drive them with the different combinations of code signing and multiple build configurations.

@steven-joruk steven-joruk requested a review from dfrankland July 3, 2021 13:53
@steven-joruk steven-joruk linked an issue Jul 3, 2021 that may be closed by this pull request
Also support validating client code requirements using the audit token
using the same APIs.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

macOS 12 introduces xpc_connection_set_peer_code_sig

2 participants