8000 fix(privacy): keep mail files owner-only and purge Flatpak staging by hanthor · Pull Request #600 · hyprlab/hylki · GitHub
[go: up one dir, main page]

Skip to content

fix(privacy): keep mail files owner-only and purge Flatpak staging - #600

Open
hanthor wants to merge 1 commit into
hyprlab:mainfrom
tuna-os:fix/private-files
Open

hanthor wants to merge 1 commit into
hyprlab:mainfrom
tuna-os:fix/private-files

Conversation

@hanthor
@hanthor hanthor commented Nov 5, 2026
Copy link
Copy Markdown
Contributor
  • The remote-content cache and the On This Computer folders (including the copy ledger) are created 0700/0600, and existing files are tightened.
  • Both log exports and the settings export are written 0600.
  • The startup purge of opened-attachment staging cleaned temp_dir()/vireo-attachments, but under Flatpak attachments are staged in $XDG_RUNTIME_DIR/app/$FLATPAK_ID/vireo-attachments, which was never purged. It now purges the directory staging actually uses.

Tests: permission tests for each writer, and the staging directory under Flatpak.

The remote-content cache, the On This Computer tree, the exported log and the settings bundle were written with umask permissions, and the startup purge cleared /tmp while the Flatpak stages opened attachments in the runtime directory.
hyprlab added a commit that referenced this pull request Nov 6, 2026
The remote-content cache, the On This Computer tree, the exported logs and the settings export were written with umask permissions. The startup purge cleared /tmp while the Flatpak stages opened attachments in the runtime directory.

Taken from the PR, plus: the purge runs only in the primary, so a second launch leaves what the running instance opened, and a directory that refuses the mode warns and stays usable instead of failing.

Co-Authored-By: James Reilly <5840441+hanthor@users.noreply.github.com>
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

0