installation/guides/chroot: fix ROOTFS method permissions #811
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
This is essentially a one-line change. It's odd that the build failed earlier but it should be fixed now. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The
tarcommand used in the "ROOTFS method" heading loses important permissions data.For example,
unix_chkpwd(a program that uses the setUID bit to allow some lockscreen programs to talk to PAM) may have missing setUID permissions, leading to user lockout.Using only tar xvf
# ls -l /mnt/usr/bin/unix_chkpwd -rwxr-xr-x 1 root root 38880 Dec 26 2023 /mnt/usr/bin/unix_chkpwdUsing Gentoo-style tar extraction
# ls -l /mnt/usr/bin/unix_chkpwd -rwsr-xr-x 1 root root 38880 Dec 26 2023 /mnt/usr/bin/unix_chkpwdThis commit updates the documentation's
tarcommand to match how Gentoo unpacks their tarballs.