Bandie/grub2-signing-extension
1
0
Fork 0
mirror of https://github.com/Bandie/grub2-signing-extension.git synced 2024-04-01 15:51:26 +00:00
Code Issues Projects Releases Wiki Activity
master
grub2-signing-extension/sbin/grub-sign

37 lines
605 B
Plaintext
Raw Permalink Normal View History

First commit and release.
2015-03-16 19:38:36 +00:00
#!/bin/bash
# grub2-sign
# Signs everything important in /boot. Depends on grub2-verify.
Using gpg's passphrase request; new script.
2018-01-12 20:46:55 +00:00
# Author: Bandie
First commit and release.
2015-03-16 19:38:36 +00:00
# Licence: GNU-GPLv3
Using gpg's passphrase request; new script.
2018-01-12 20:46:55 +00:00
function sign(){
Excluding the EFI directory. Fixes #10
2021-02-13 12:54:17 +00:00
for f in $(find /boot -iname "efi" -prune -o -type f -print)
Using gpg's passphrase request; new script.
2018-01-12 20:46:55 +00:00
do
if gpg --detach-sign $f
then
echo $f signed.
else
return 1
fi
done
return 0
}
Comments and words.
2015-03-17 06:23:23 +00:00
Using gpg's passphrase request; new script.
2018-01-12 20:46:55 +00:00
# Running grub2-verify first to prevent bad people and double signing
Follow best practices for bash - Use native bash math where doing so improves readability. - Avoid illegal exit status codes (666 in impossible scenario). - Avoid useless use of cat (`cat foo | bar` vs the more efficient `bar <foo`). - Avoid needless echo pipelines (`echo foo | bar` vs `bar <<<"$foo"`). - Never use a for loop to iterate over output from `find`; `for` loops depend on string-splitting, which is only available with globbing behavior. See http://mywiki.wooledge.org/DontReadLinesWithFor - Use `read -s` to silence feedback rather than playing around with `stty`. - Use `tput` to retrieve color codes correct for the current terminal rather than assuming a terminal compatible with ANSI color codes. - Use a expression compatible with BSD `tr` in "passphrase-shredding" code. (BTW, I very much doubt that this code actually does any good; it's not a reasonable expectation that a new string assigned to a variable will actually be placed at the same location in memory). - Implementations of `echo` which do anything other than print `-e` on output when `echo -e` is run are nonconformant with the POSIX spec for echo. Similarly, `echo -n` behavior is not defined by the standard. Avoid relying on either of these. (See http://pubs.opengroup.org/onlinepubs/009604599/utilities/echo.html, particularly the APPLICATION USAGE section). - Always quote expansions to prevent string-splitting and glob-expansion (`"$i"`, not `$i`). - Avoid `some_command; if [ $? -eq 0 ]; then` when `if some_command; then` can be used instead.
2015-12-30 21:32:46 +00:00
echo "Running grub2-verify to check if everything is unsigned..." >&2
Bug: Changed script name
2020-01-08 16:54:57 +00:00
grub-verify
Follow best practices for bash - Use native bash math where doing so improves readability. - Avoid illegal exit status codes (666 in impossible scenario). - Avoid useless use of cat (`cat foo | bar` vs the more efficient `bar <foo`). - Avoid needless echo pipelines (`echo foo | bar` vs `bar <<<"$foo"`). - Never use a for loop to iterate over output from `find`; `for` loops depend on string-splitting, which is only available with globbing behavior. See http://mywiki.wooledge.org/DontReadLinesWithFor - Use `read -s` to silence feedback rather than playing around with `stty`. - Use `tput` to retrieve color codes correct for the current terminal rather than assuming a terminal compatible with ANSI color codes. - Use a expression compatible with BSD `tr` in "passphrase-shredding" code. (BTW, I very much doubt that this code actually does any good; it's not a reasonable expectation that a new string assigned to a variable will actually be placed at the same location in memory). - Implementations of `echo` which do anything other than print `-e` on output when `echo -e` is run are nonconformant with the POSIX spec for echo. Similarly, `echo -n` behavior is not defined by the standard. Avoid relying on either of these. (See http://pubs.opengroup.org/onlinepubs/009604599/utilities/echo.html, particularly the APPLICATION USAGE section). - Always quote expansions to prevent string-splitting and glob-expansion (`"$i"`, not `$i`). - Avoid `some_command; if [ $? -eq 0 ]; then` when `if some_command; then` can be used instead.
2015-12-30 21:32:46 +00:00
if (( $? < 2 )); then
echo "Run grub2-unsign first." >&2
First commit and release.
2015-03-16 19:38:36 +00:00
exit 1
fi
Comments and words.
2015-03-17 06:23:23 +00:00
Using gpg's passphrase request; new script.
2018-01-12 20:46:55 +00:00
if ! sign
then
sign
else
echo -e "\nDone!"
Follow best practices for bash - Use native bash math where doing so improves readability. - Avoid illegal exit status codes (666 in impossible scenario). - Avoid useless use of cat (`cat foo | bar` vs the more efficient `bar <foo`). - Avoid needless echo pipelines (`echo foo | bar` vs `bar <<<"$foo"`). - Never use a for loop to iterate over output from `find`; `for` loops depend on string-splitting, which is only available with globbing behavior. See http://mywiki.wooledge.org/DontReadLinesWithFor - Use `read -s` to silence feedback rather than playing around with `stty`. - Use `tput` to retrieve color codes correct for the current terminal rather than assuming a terminal compatible with ANSI color codes. - Use a expression compatible with BSD `tr` in "passphrase-shredding" code. (BTW, I very much doubt that this code actually does any good; it's not a reasonable expectation that a new string assigned to a variable will actually be placed at the same location in memory). - Implementations of `echo` which do anything other than print `-e` on output when `echo -e` is run are nonconformant with the POSIX spec for echo. Similarly, `echo -n` behavior is not defined by the standard. Avoid relying on either of these. (See http://pubs.opengroup.org/onlinepubs/009604599/utilities/echo.html, particularly the APPLICATION USAGE section). - Always quote expansions to prevent string-splitting and glob-expansion (`"$i"`, not `$i`). - Avoid `some_command; if [ $? -eq 0 ]; then` when `if some_command; then` can be used instead.
2015-12-30 21:32:46 +00:00
fi
Additional exit codes added + better shredding
2015-03-17 06:54:03 +00:00
Reference in New Issue Copy Permalink