Skip to content
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

Catalina Security - Input monitoring vs accessibility #157

Closed
RicardoPassavantes opened this issue May 11, 2020 · 2 comments
Closed

Catalina Security - Input monitoring vs accessibility #157

RicardoPassavantes opened this issue May 11, 2020 · 2 comments

Comments

@RicardoPassavantes
Copy link

Giving Unshakey accessibility full computer control in the Privacy & Security settings makes me nervous - can/has it been updated to support Input Monitoring?

@aahung
Copy link
Owner

aahung commented May 19, 2020

it makes sense, thanks!

@aahung
Copy link
Owner

aahung commented Aug 5, 2020

According to the WWDC 2019 "Advances in macOS Security" where you can find the following transcript:

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.

@aahung aahung closed this as completed Aug 5, 2020
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

No branches or pull requests

2 participants