Hacktoberfest 2026:维护者为十月标记出来的 issue,仍然开放、适合新手。 浏览 Hacktoberfest issue

Security concerns about internet acces of skhd on MacOS 15 Sequoia

未关闭
#369 1 条评论 9 个 reaction 已指派 0 人 在 GitHub 查看

还没有人认领这个 Issue。

评估

难度
4/5
预计耗时
3-5 天
新手友好度
25/100
Issue 类型
缺陷
描述清晰度
需要澄清
活跃度
停滞
技术栈
c, macos

调研方向

该 issue 没有指明源文件、测试或入口点。首先使用 LuLu 在 macOS 15 上复现该行为,包括阻止 skhd 以及更改 Local Network 权限,然后检查 skhd 如何与这些系统控制机制交互。完成标准是确定 skhd 是否导致了无关的网络中断,并记录或修正该行为。

由索引模型根据 Issue 内容生成。

描述

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.

主要语言
C
星标
8.1k
派生
237
PR 合并指标
30 天内没有已合并 PR

环境准备

这个项目没有提供开发容器、Dockerfile 或贡献指南,环境需要你自己搭建:先看它的 README,通用步骤见我们的新手贡献指南。

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

asmvik/skhd 的其他 Issue

查看 asmvik/skhd 的全部 Issue

相似的 Issue

更多 C Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。