Skip to content

docs: add the security tradeoffs to the FAQ - #444

Merged
JaceThings merged 1 commit into
mainfrom
docs/security-tradeoffs
Nov 13, 2026
Merged

JaceThings merged 1 commit into
mainfrom
docs/security-tradeoffs

Conversation

@JaceThings

Copy link
Copy Markdown
Owner

What

Adds a "What are the security tradeoffs?" entry to the README FAQ, right under "Is it safe?".

Why

Closes #441. "Is it safe?" only covers privacy. The new entry says what patching changes about Dia's own protection: no hardened runtime, a dylib loaded from Application Support, the local signing certificate, how DiaTweaks updates are checked, how the Passwords tweaks reach the password managers, when Dia updates are looked for, and what Restore leaves behind.

Proof

Docs only. Each line was checked against the code: sign() and stageTweaks in src/diapatch/main.m, src/dylib/Updates/Updates.m, and the update level labels in src/dylib/Settings/SoftwareUpdate.m. codesign -d shows flags=0x0 on the patched Dia and runtime on the original.

Tested on

  • Dia: 1.57.0 (90921)
  • macOS: 27.0.1

Checklist

  • I tried to break this and fixed what I found
  • It works with tabs in the sidebar and tabs at the top
  • It works with each tweak on and off

@JaceThings
JaceThings merged commit 5970dd9 into main Nov 13, 2026
2 checks passed
@JaceThings
JaceThings deleted the docs/security-tradeoffs branch November 13, 2026 14:36
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

Successfully merging this pull request may close these issues.

Make the security tradeoffs of using this tool clearer

1 participant