So users should be somewhat used to them, which is fortunate as the error message is rather misleading as we don't need this for accessibility features.Įvent taps have been around for forever, but AXIsProcessTrustedWithOptions() was added in macOS 10.9. Googling the error message you get ('Foo.app would like to control this computer using accessibility features') you get some hits saying that applications like Steam and Dropbox do this. We just need to attempt to do set up for the event tap again.

Once the user does that things start to work right away. It allows the user to quickly open the correct part of the system settings and give us the necessary access. And I can confirm we don't have privileges to do this by default, and AXIsProcessTrustedWithOptions() will indeed prompt the user in that case. This is a system installed service though so it might have a hard coded back door for this.Ī quick test shows that event taps seem to work fine for this. It's unclear how it gets the extra privileges it needs. There is nothing about PushSymbolicHotKeyMode() among the imported symbols. > RFBEventHelper.bundle/Contents/MacOS/RFBEventHelperd: > $ cbrun os圆4 x86_64-apple-darwin10-otool -v -I RFBEventHelper.bundle/Contents/MacOS/RFBEventHelperd | grep Event

It seems to use the EventTap system, given that it imports those symbols: > claim it has a background service called RFBEventHelper that is essential

> client does since it apparently forwards all key presses. > We could also see if we can figure out what Apple's own screen sharing (In reply to Pierre Ossman from comment #8)

Nomachine shortcuts