Cant create a macOS PPPC/TCC Approval for xbar?
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 18.1k
- Forks
- 656
- PR merge metrics
- No merged PRs in 30d
Description
When xbar launches automatically, it displays a pop-up in the macOS Finder stating that "xbar needs to control the SystemEvents app..."
This is a common PPPC (Privacy Preferences Policy Control) approval that end users must acknowledge when multiple apps or services try to talk to each other in various (potentially sneaky) ways. This security measure started in macOS Mojave.
Rather than approve xbar manually, for a single end-user, I need to pre-approve it automatically via my MDM (Jamf) using a PPPC MDM configuration profile for mass deployment. This is very common in enterprises (I have over 20 PPPC profiles for various apps and services).
Typically I use a tool named PPPC Utility (https://github.com/jamf/PPPC-Utility) to build these profiles. However, PPPC cannot build a profile for xbar. This is the first time I have ever seen an app fail. The error is:
Failed to get designated code requirement. The executable may not be signed. Error: The operation couldn’t be completed. (OSStatus error -67062.)
I believe this clearly means xbar is from an unrecognized developer (not siged etc).
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by investigating how xbar is signed and why PPPC Utility reports that it cannot get a designated code requirement. Confirm the macOS packaging or signing change needed for Jamf to generate a PPPC profile and verify that the resulting xbar application can be pre-approved.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, macos
- Domain
- desktop, operating-systems, security
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100