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

Security concerns about internet acces of skhd on MacOS 15 Sequoia #369

Open
Muskra opened this issue Oct 1, 2024 · 0 comments
Open

Security concerns about internet acces of skhd on MacOS 15 Sequoia #369

Muskra opened this issue Oct 1, 2024 · 0 comments

Comments

@Muskra
Copy link

Muskra commented Oct 1, 2024

Hi i'm a user of skhd since one year now, really nice piece of software, works great for my use cases.
Since yesterday, i've upgraded my computer to the Sequoia 15.x and i'm facing issues with the tool. I'm using LuLu from Objective See that you can check here to monitor services and telemetry i don't want to mess with on my network.

So when i've upgraded to Sequoia, i'm trying to brew an update then upgrade, nothing else works. Seem's that i don't have any network access. I then look at my ip config and it's fine, DNS don't seem's to receive any packets from my computer. Then i look at the rules on LuLu and i've searched for like 3 hours to see which of the rules are blocking internet access. Turns up, i've blocked skhd in the past and it seem's that blocking skhd is now blocking all the network traffic to go out. Why is that ? I don't want an input reader to connect to internet. I also needed to grant permission to skhd to see network devices (in "Privacy & Security's Local Network" tab of MacOS settings) to see my router and printers again. Why ? This kind of tools should never manage network in any way.

Can you walk me through ? I want to understand what's going on there, i'm seeing this as a security issue (from my perspective). I'm not sure to trust this software because of these weird behaviors. An input reader should never ever connect to internet. This could be exploited and used as Keylogger and i don't like this idea.

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

1 participant