Skip to content

[Security] Keep the update transcript out of world-writable /tmp - #9084

Closed
Chessing234 wants to merge 3 commits into
omacom:quattrofrom
Chessing234:security/update-log-private-runtime
Closed

Chessing234 wants to merge 3 commits into
omacom:quattrofrom
Chessing234:security/update-log-private-runtime

Conversation

@Chessing234

@Chessing234 Chessing234 commented Aug 30, 2026 •

Copy link
Copy Markdown
Contributor

Summary

  • omarchy update always wrote /tmp/omarchy-update.log
  • A local user who pre-created that path as a symlink could redirect script(1) into the victim's files
  • Stage the log under $XDG_RUNTIME_DIR/omarchy-update/ (or a 0700 cache under ~/.cache/omarchy/update); analyze-logs follows the same path and refuses symlinks

Test plan

  • bash test/shell.d/update-log-path-test.sh
  • Run omarchy update -y (or a dry path) and confirm the transcript is not under /tmp/omarchy-update.log

A pre-created /tmp/omarchy-update.log symlink let another local user
redirect script(1) into the victim's files. Stage the log under
XDG_RUNTIME_DIR (or a 0700 cache under \$HOME).
@Chessing234

Copy link
Copy Markdown
Contributor Author

@dhh @ryanrhughes ready for review

@Chessing234

Copy link
Copy Markdown
Contributor Author

folded into #12077 — more /tmp staging hardening in one place.

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.

1 participant