[Bug]: macOS crash persists in Herd 2.0.3 after preferences reset — possible SecureDefaults key access failure

未关闭
  • 哪里不对？
#1,794 0 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

还没有人认领这个 Issue。

评估

难度
5/5
预计耗时
一周以上
新手友好度
12/100
Issue 类型
缺陷
描述清晰度
需要澄清
活跃度
活跃
技术栈
macos
领域
desktop, security

调研方向

The payload names no source files or tests, only a native macOS crash with SIGTRAP at image-relative offsets and a question about SecureDefaults licence storage. Start by reading the referenced comment on #1036 and the crash report, then check whether the offsets can be symbolicated against the 2.0.3 binary. Done would mean a confirmed root cause or a maintainer-approved recovery procedure, which needs maintainer access and is not a first-timer task.

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

描述

macOS
Platform

macOS

Operating system version

macOS 26.5 (25F71)

System architecture

ARM64 — Apple M3, MacBook Air (Mac15,13), 16 GB RAM

Herd Version

2.0.3 (72); originally affected on 2.0.0 (69)

PHP Version

Not established; this is a crash of the native Herd application.

Bug description

Herd 2.0.0 started crashing immediately on launch. Backing up and resetting its preferences allowed it to open and update to 2.0.3. However, 2.0.3 subsequently crashed, reopened successfully, then crashed again about 90 seconds after launch.

This resembles #1036 and the maintainer’s diagnosis of inaccessible licence information associated with missing SecureDefaults Keychain entries:
https://github.com/beyondcode/herd-community/issues/1036#issuecomment-2382435578

The preferences reset recommended there restored launchability here but did not resolve the recurring crashes.

Steps taken and observed results
  1. Launched with open /Applications/Herd.app --args --enable-logfile. Initially, no debug log was created before the crash.
  2. Verified the app using codesign --verify --deep --strict --verbose=4 /Applications/Herd.app outside the diagnostic sandbox. Verification passed, including embedded components. Signing identity: Beyond Code GmbH (8Z259RPWAC).
  3. Queried the login Keychain status: unlocked, readable and writable. GUI searches under login for Herd and beyond returned no entries. A command-line metadata inspection found no SecureDefaults entries in the login Keychain either.
  4. Attempted item access-control inspection; macOS returned “The user name or passphrase you entered is not correct”, so individual item permissions could not be verified.
  5. Exported and validated a preferences backup, then ran defaults delete de.beyondco.herd.
  6. Relaunched Herd and completed its offered update to 2.0.3. The Applications window opened with existing sites visible.
  7. Herd crashed again. Reopening worked, but another crash followed roughly 90 seconds later.

After the reset, the debug log existed. Its inspected tail contained repeated Terminate observer called for process messages.

A deterministic trigger beyond launching/reopening has not been established. Expected: Herd opens and remains running. Actual: it opens but subsequently terminates with SIGTRAP.

Diagnostic findings

During the earlier 2.0.0 launches, macOS logs showed CSSMERR_CSP_OPERATION_AUTH_DENIED alongside Keychain operations shortly before the crash.

Disassembly of the failing code appears consistent with SecureDefaults’ encryption-key access path. This is an inference from binary inspection, not a symbolicated or confirmed root cause.

The original 2.0.0 crashes occurred immediately on the main thread. The two subsequent 2.0.3 reports have identical top-frame offsets and occur on com.apple.root.user-initiated-qos.

Latest crash details
Crash time:       2026-11-02 20:05:08.1423 +0000
Launch time:      2026-11-02 20:03:38.0130 +0000
Version:          2.0.3 (72)
Incident ID:      663911F2-7C46-476E-B2D8-ADF2013797CD
Exception:        EXC_BREAKPOINT (SIGTRAP)
Exception codes:  0x0000000000000001, 0x000000010308b280
Termination:      SIGNAL 5 — Trace/BPT trap
Crashed thread:   11
Queue:            com.apple.root.user-initiated-qos
Image base:       0x102aac000
Binary UUID:      7fe98419-a95e-35e0-9a4f-53b08f1bf64b
SIP:              enabled

Top Herd frames (image-relative decimal offsets):
0  +6156928
1  +6159924
2  +6151808
3  +4641764
4  +573076
5  +5209656
6  +5171380
7  +7700524
8  +7692484
9  +7711220
10 +7715304
11 +117612

These offsets match the preceding 2.0.3 crash at 20:02:35.

Could you symbolicate these frames and confirm whether SecureDefaults/licence storage is involved? What is the supported recovery procedure when resetting preferences only restores access temporarily?

主要语言
没有语言数据
星标
125
派生
1
30 天内没有已合并 PR

环境准备

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

从这里开始

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

beyondcode/herd-community 的其他 Issue

查看 beyondcode/herd-community 的全部 Issue

相似的 Issue

更多 Desktop Dev Issue

把新 issue 发到你的邮箱

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