You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Giving Unshakey accessibility full computer control in the Privacy & Security settings makes me nervous - can/has it been updated to support Input Monitoring?
The text was updated successfully, but these errors were encountered:
If I change the listenOnly parameter to defaultTap, like that, CGEventTapCreate now creates a modifying event tab, where the callback can alter the event stream. And this means now your app has a way to influence what events are delivered to the rest of the system, where a listen-only event requires authorization for input monitoring, a modifying event app requires authorization for accessibility features.
Accessibility feature is mandatory for Unshaky to function since "blocking" key presses will require not only "listen-only" event tap, but also the ability to modify the event.
To make you less nervous about such "excessive" permission, I am afraid you will need to compile Unshaky from the source code yourself.
Giving Unshakey accessibility full computer control in the Privacy & Security settings makes me nervous - can/has it been updated to support Input Monitoring?
The text was updated successfully, but these errors were encountered: