Skip to content

Conversation

@kitlith
Copy link
Contributor

@kitlith kitlith commented May 14, 2025

The current behavior seems to date back to the initial commit of the original C version of this tool:

teohhanhui/krun.legacy@01ae759#diff-ba1f55157a5e8661da39884a2669de7c912ff94d98134d6d520ed0468670e39bR198

Is anything relying on this extra permissiveness? I didn't notice any breakage in a quick test after patching this (consisting of launching Balatro through steam, nevermind that I normally just use the native build of love to run balatro) but that doesn't mean much.

From the spec: "Its Unix access mode MUST be 0700". Some software
will check this and throw an error if it isn't. For instance, the
xdg crate returns an `Err(XdgRuntimeDirInsecure(/*...*/))` under
muvm.

Signed-off-by: Kitlith <kitlith@kitl.pw>
@kitlith kitlith force-pushed the xdg_runtime_700 branch from 654ea3e to fe3fc43 Compare May 14, 2025 06:47
@teohhanhui
Copy link
Collaborator

Relevant section of the spec:

$XDG_RUNTIME_DIR defines the base directory relative to which user-specific non-essential runtime files and other file objects (such as sockets, named pipes, ...) should be stored. The directory MUST be owned by the user, and they MUST be the only one having read and write access to it. Its Unix access mode MUST be 0700.

https://specifications.freedesktop.org/basedir-spec/latest/

@slp slp merged commit ef920fb into AsahiLinux:main Jun 12, 2025
1 check passed
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.

3 participants