-
-
Notifications
You must be signed in to change notification settings - Fork 185
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
track files in /boot in kexec_tree.txt #1262
Commits on Jan 14, 2023
-
Configuration menu - View commit details
-
Copy full SHA for accd9f4 - Browse repository at this point
Copy the full SHA accd9f4View commit details -
Configuration menu - View commit details
-
Copy full SHA for 60df237 - Browse repository at this point
Copy the full SHA 60df237View commit details -
initrd kexec_tree: fix various escaping issues
Attempt to fix the following issues: 1. unescaped file names may let an attacker display arbitrary whiptail prompts --> escape, original code by @JonathonHall-Purism 2. whiptail itself allows escape characters such as \n --> use an escape character not used by whiptail, i.e. # 3. performance issues caused by diff'ing too early --> only generate a diff to display to the user, if an actual issue is found
Configuration menu - View commit details
-
Copy full SHA for f52466e - Browse repository at this point
Copy the full SHA f52466eView commit details -
initrd: speed up non-GUI booting
by not generating the kexec_tree diff in that case
Configuration menu - View commit details
-
Copy full SHA for e368c3f - Browse repository at this point
Copy the full SHA e368c3fView commit details -
initrd: work around a bug in busybox sha256sum
busybox sha256sum will create a checksum file for uncommon file names (e.g. /boot/foo"$\n"bar), but fail to verify that exact file. https://bugs.busybox.net/show_bug.cgi?id=14226 Thus disallow all files in /boot/ with strange file names at the time of signing for now. Verifying in the presence of new files with such file names in /boot/ is no issue for the kexec_tree verification due to the previously implemented escaping mechanism.
Configuration menu - View commit details
-
Copy full SHA for 4ce8f66 - Browse repository at this point
Copy the full SHA 4ce8f66View commit details -
initrd: call assert_signable earlier
No need to check for the GPG card first.
Configuration menu - View commit details
-
Copy full SHA for c65d6b9 - Browse repository at this point
Copy the full SHA c65d6b9View commit details -
initrd: assert_signable: use recovery() instead of die()
and display some more information to the user, if available
Configuration menu - View commit details
-
Copy full SHA for 2ae7f53 - Browse repository at this point
Copy the full SHA 2ae7f53View commit details -
initrd: escape_zero: allow some more characters
Since it's not supposed to be shell safe, just display safe inside double quotes, we can allow some more characters. Also fix the escape character not being escaped.
Configuration menu - View commit details
-
Copy full SHA for d07df1e - Browse repository at this point
Copy the full SHA d07df1eView commit details