From 3627833f615935fb4784be2dbf648cb812b59f3d Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Jakobus=20Sch=C3=BCrz?= Date: Wed, 17 Jul 2019 23:31:52 +0200 Subject: [PATCH] README angepasst, modules.example added --- .gitignore | 1 + README.md | 20 ++++++++++++++++---- modules.example | 5 +++++ 3 files changed, 22 insertions(+), 4 deletions(-) create mode 100644 modules.example diff --git a/.gitignore b/.gitignore index ef720c7..db4f3f4 100644 --- a/.gitignore +++ b/.gitignore @@ -1,2 +1,3 @@ *.der *.priv +modules diff --git a/README.md b/README.md index 2a1dc74..fe58371 100644 --- a/README.md +++ b/README.md @@ -3,25 +3,37 @@ * Create key-pair ``` - create_module_key.sh -c + ./sign-modules.sh -c ``` + you get asked for a Password for the new key. Remember it, you'll need it a reboot once to confirm the new installed key. * Sign your proprietary modules ``` - create_module_key.sh -s \[ \][ \]... + Usage sign modules: + ./sign-modules.sh [] []... + ./sign-modules.sh -k [] []... + ./sign-modules.sh -k -f + ./sign-modules.sh -f + + -k output of »uname -r« + if not given, it takes current kernelversion + + -f plaintext file with newlineseparated list of modules to sign ``` * Reboot + If you have a Dualboot with Windows and Bitlocker, you have to type in you Recreation-Key for Bitlocker on first boot in Windows, because you added a key to UEFI Every time you install a new kernel, you have to boot to the new kernel and run - create_module_key.sh -s \[ \][ \]... + ``` + ./sign-modules.sh -k -f + ``` * Reboot again. -This script creates a key. You need it for signing every module for every new kernel you install on your machine!!! Keep it save! diff --git a/modules.example b/modules.example new file mode 100644 index 0000000..2cbd644 --- /dev/null +++ b/modules.example @@ -0,0 +1,5 @@ +vboxdrv +vboxnetflt +vboxnetadp +vboxpci +acpi_call