Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

default SUID for umount (un-mount) may be incorrect #284

Closed
the-moog opened this issue Dec 6, 2024 · 2 comments · Fixed by #285
Closed

default SUID for umount (un-mount) may be incorrect #284

the-moog opened this issue Dec 6, 2024 · 2 comments · Fixed by #285

Comments

@the-moog
Copy link

the-moog commented Dec 6, 2024

As it is required for systemd --user mount units, I think the default configuration for permission hardening of
umount should be in the same file as mount in the file /etc/permission-hardener.d/25_default_whitelist_mount.conf.

It's bugged me for ages why network mounts can't restart. Just realised why.

Also (not sure what it's supposed to be) but in the same file, I see mode 745 on mount which means group members can't execute it but anybody else can. Surely it should be 755 or 744? I assume this is as shipped as I've never changed it?

@adrelanos
Copy link
Member

Ok, seems logical to treat mount and umount the same way.

, I see mode 745 on mount which means group members can't execute it but anybody else can.

Everyone includes group members. Therefore very minor issue.

Surely it should be 755 or 744?

755 seems good.

@adrelanos
Copy link
Member

See #285

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 a pull request may close this issue.

2 participants