Linux Kernel Runtime Guard (LKRG) in Qubes OS Debian or Kicksecure ™ for Qubes VMs
Linux Kernel Runtime Guard (LKRG) protects the kernel. It provides security through diversity and has a similar effect to running an uncommon operating system (kernel). 
LKRG renders whole classes of kernel exploits ineffective, while making other exploits less reliable and more difficult to write; see features and security. LKRG was developed by a security professional with reviews undertaken by other high profile security professionals; see authorship. For further information, refer to the main LKRG entry.
For all other platforms , see LKRG.
Qubes VM Kernel
Since LKRG is a kernel module, it is required (and advisable) to reconfigure the VM to use a Qubes VM kernel. 
Any issues with Qubes VM kernel should not be confused with LKRG. Otherwise, LKRG could be falsely suspected of causing unrelated issues, which wastes time in successfully completing the configuration.
- Follow the Qubes OS Installing kernel in Debian VM instructions.
- Ensure the Qubes VM kernel is functional before proceeding -- Qubes VM kernel issues should be raised at Qubes support and not in Kicksecure ™ forums.  
- Reboot dom0 with Qubes VM kernel. This is because Qubes VM kernel might break unrelated things such as the USB VM. 
- Once the Qubes VM kernel is functional, proceed with the following instructions.
Add Signing Key
The LKRG installation procedure is complete. Interested users can learn more, consider additional hardening and so on; see here for further information.
Credits and Source Code
This website with Qubes instructions and LKRG Debian Package Website is the software fork homepage for LKRG, with a focus on easy installation, added user documentation, and integration with Kicksecure, Debian, Whonix and other distributions. The software fork source code can be found here.
- cannot compile LKRG (Linux Kernel Runtime Guard) with Qubes dom0 kernel / broken gcc plugins structleak_plugin.so latent_entropy_plugin.so This probably occurs due to this recently closed issue which has only filtered through to Qubes OS master branches, but not the stable branches: kernel-devel package have broken gcc plugin. The dom0 kernel compilation bug might be fixed after upgrades. It is unclear if it would then be advisable to use dom0 kernel.
- Qubes feature request: Simplify and promote using in-vm kernel
- As experienced firsthand by Kicksecure ™ developer Patrick Schleizer.
See Secure Downloads to understand why
curland the parameters
--tlsv1.3 --proto =httpsare used instead of
Placing an additional signing key into folder
/usr/share/keyringsby itself alone has no impact on security as this folder is not automatically used by Debian's APT by default. Only when an APT sources list configuration file points to folder
signed-bykeyword the signing key will be actually used. Therefore deleting keys in
/usr/share/keyringsis optional if intending to disable an APT repository. See also APT Signing Key Folders.