Automatic VirtualBox module signing for UEFI
These steps are for all those people who hate to sign the Virtualbox modules every time and don’t want to disable UEFI.
These steps are for all those people who hate to sign the Virtualbox modules every time and don’t want to disable UEFI.
I’m assuming you are already able to program and at least had a look at C++.
For example I won’t explain why int main(int argc, char *argv[]) is in the C++ source code.
If you create a "Qt Console Application" you will have the following code:
I just encountered the problem that I have to type two passwords at startup, for two encrypted disks. My first disk is encrypted through the Ubuntu installer. After some searching I found the perfect solution for that task. In German its called "Schlüsselableitung", in English derived keys. But perfect solutions often have a big issue why they don’t work, like here. I’m using Ubuntu 16.04 which uses ´systemd´, and that has problems with derived keys. So I found the second most perfect solution for me, using a key-file. Some people argue that this is a security issue, but the derived key is also obtainable with root rights, just like a key-file. And by the way, your private keys of your certificates are also stored on that disks and nearly nobody complains about that.
The one thing that confuses the most people in the beginning is the Signal & Slot mechanism of Qt. But it’s actually not that difficult to understand. In general Signals & Slots are used to loosely connect classes. Illustrated by the keyword emit, Signals are used to broadcast a message to all connected Slots. If no Slots are connected, the message "is lost in the wild". So a connection between Signals & Slots is like a TCP/IP connection with a few exceptions, but this metaphor will help you to get the principle. A Signal is an outgoing port and a Slot is an input only port and a Signal can be connected to multiple Slots.