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

Why is sarus requiring root permissions for things that are outside of sarus? #33

Open
haampie opened this issue Jun 30, 2023 · 1 comment
Labels
question Further information is requested

Comments

@haampie
Copy link

haampie commented Jun 30, 2023

#0   checkThatPathIsRootOwned at "SecurityChecks.cpp":78 Path "/home/harmen/spack/opt/spack/linux-ubuntu22.10-zen2/gcc-12.2.0/squashfs-4.5.1-kyy4hxwwoqqwhrws35zhcgcqcmn56yah/bin/mksquashfs" must be owned by root in order to prevent other users from tampering its contents. Found uid=1000, gid=1000.

Why?

@Madeeks
Copy link
Member

Madeeks commented Jul 6, 2023

Hi @haampie,
the intention of the feature, as part of the security checks, is to reduce the possibility of exploits through 3rd party binaries, which in several cases are executed with root privileges by Sarus.

Notice that the specific constraint you are referring to (root ownership of mksquashfs) was relaxed in version 1.5.2, since mksquashfs is only used by unprivileged commands.

@Madeeks Madeeks added the question Further information is requested label Jul 6, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
question Further information is requested
Projects
None yet
Development

No branches or pull requests

2 participants