-
Notifications
You must be signed in to change notification settings - Fork 3
fix: add code signing requirements to xpc connections #206
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: ethan/networking-in-launchdaemon
Are you sure you want to change the base?
fix: add code signing requirements to xpc connections #206
Conversation
Warning This pull request is not mergeable via GitHub because a downstack PR is open. Once all requirements are satisfied, merge this PR as a stack on Graphite.
This stack of pull requests is managed by Graphite. Learn more about stacking. |
c7dbde8
to
ef8832a
Compare
ea87f52
to
5bf788f
Compare
5bf788f
to
547fd97
Compare
ef8832a
to
e32d7de
Compare
public static let xpcPeerRequirement = "anchor apple generic" + // Apple-issued certificate chain | ||
" and certificate leaf[subject.OU] = \"" + expectedTeamIdentifier + "\"" // Signed by the Coder team |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Probably should go onto it's own class since it seems unrelated to the binary signature validation.
547fd97
to
6687411
Compare
eebf562
to
291e5a1
Compare
6687411
to
ef370db
Compare
Continues to address #201.
I've manually tested that this change prevents binaries not signed by the Coder Apple development team from connecting to the Helper over XPC.
Most of the PR diff is me moving the validator out of
Download.swift
and intoValidate.swift