Gentoo Hardened is a Gentoo project that offers multiple additional security services on top of the well-known Gentoo Linux installation. Although each of them can be selected separately, Gentoo Hardened enables several risk-mitigating options in the toolchain, supports PaX, grSecurity, SELinux, TPE and more.
Whether you are running an Internet-facing server or a flexible workstation, when you are dealing with multiple threats you will want to harden your system further than just automatically applying the latest security patches. Hardening a system means that you take additional countermeasures against attacks and other risks and is usually a combined set of activities you perform on the system.
Within Gentoo Hardened, several projects are active that help you further harden your Gentoo system through
- Enabling specific options in the toolchain (compiler, linker ...) such as forcing position-independent executables (PIE), stack smashing protection and compile-time buffer checks.
- Enabling PaX extensions in the Linux kernel, which offer additional protection measures like address space layout randomization and non-executable memory.
- Enabling grSecurity extensions in the Linux kernel, including additional chroot restrictions, additional auditing, process restrictions, etc..
- Enabling SELinux extensions in the Linux kernel, which offers a Mandatory Access Control system enhancing the standard Linux permission restrictions.
- Enabling Integrity related technologies, such as Integrity Measurement Architecture, for making systems resilient against tampering
Of course, this includes the necessary userspace utilities to manage these extensions.
Switching to a Hardened Profile
Select a hardened profile, so that package management will be done in a hardened way.
By choosing the hardened profile, certain package management settings (masks, USE flags, etc) become default for your system. This applies to many packages, including the toolchain. The toolchain is used for building/compiling your programs, and includes: the GNU Compiler Collection (GCC), binutils (linker, etc.), and the GNU C library (glibc). By re-emerging the toolchain, these new default settings will apply to the toolchain, which will allow all future package compiling to be done in a hardened way.
The above command rebuilt GCC, which can now be used to compile hardened software. Make sure that the hardened option is selected for GCC.
In the example output above, the hardened GCC profile is the one without a suffix. If you want to disable PIE or SSP, choose the relavent hardenedno(pie|ssp) or both, hardenednopiessp. The vanilla profile is of course the one with hardening disabled. Finally source your new profile settings:
If you use the "prelink" package, remove it, since it isn't compatible with the hardened profile:
Now you can reinstall all packages with your new hardened toolchain:
Install hardened kernel sources, so that the kernel will *manage your running system* in a hardened way (especially using PaX):
Now configure/compile the sources and add the new kernel to your boot manager (ie., GRUB).
Tips & Tricks
Hardened Gentoo/Grsecurity chroot
If you want to chroot to a copied environment where the CONFIG_GRKERNSEC_CHROOT is enabled you must use the cd grub and change the root(cd) kernel(cd) initrd(cd) setting to from (cd) to (hdx,y).
Now you can install the grub environment.
Per Package Hardening Settings
Changing the GCC profile to deal with specific packages can be a pain. A way to avoid this is to set per-package C(XX)FLAGS using package.env. Create the file /etc/portage/env/nossp and add to that:
To allow for disabling PIE, create and add to /etc/portage/env/nopie:
Finally add the package you want to disable either PIE or SSP for to /etc/portage/package.env and the relevant /etc/portage/env/<filename>, for this example sys-libs/zlib is used here:
- Gentoo Hardened Project
- Gentoo Hardened SELinux Project