I am too lazy to research it and still wondering. Can someone give me a basic explanation of it?
You don’t mention any specific distro, but I’m guessing it’s pretty similar across distros. And since Arch tends to have good documentation, I’ve focused mostly on Arch. (I use Arch BTW. Fight me. :wink:)
The differences are that a different set of configuration options were selected when building the Kernel. All differences in configuration were selected with security in mind.
Here is a full list with lots of details but just vaguely (in roughly the same order as they are on the Arch page):
- It takes some special memory management steps to mitigate buffer overflow and stack overflow kind of vulnerabilities that might exist in other programs on the system.
- It locks down access to some information about specific kernel processes to prevent malicious programs from accessing those kernel processes. (And the wiki page says specifically that this doesn’t really help much unless you compile your own kernel, but yeah.)
- Locks down “BPF” which, honestly, I don’t know much about. Has something to do with firewalls?
- Prevents one application from getting internal data about another application (like happens with programs like strace or gdb.)
- Hides other users’ processes from your current user.
- Prevents loading of unsigned kernel modules.
- Turns off a feature that lets you replace a running kernel with a newer kernel version without restarting the whole computer.
- Enables “Kernel lockdown mode” which "strengthens the boundary between what the root user can access and kernel space.
- Enables “LKRG” which is kindof an “intrusion detection system for the Linux kernel.”
- Disables the emergency shell that can otherwise be used to debug and recover when your system fails to boot. (But could also be used to do evil things if an adversary has physical access to the computer, I think?)
So, all fairly technical stuff, but just locks stuff down and locks down things to improve overall security at the expense of some functionality. Some applications just straight won’t work with a hardened kernel. (skypeforlinux-stable-bin is an example of a program that the Arch page listed above gives that just won’t work.)
- Locks down “BPF” which, honestly, I don’t know much about. Has something to do with firewalls?
BPF (more importantly it’s successor, eBPF) allows (very specific, automatically verified) programs to run in kernel space, triggered by various events. Mostly used for networking stuff.
I’m running self compiled hardened kernel and I enabled kernel lockdown mode. Before that it was disabled. Maybe Arch team disabled it.
deleted by creator
I wouldn’t recommend OpenBSD as it is fairly obscure compared to Linux. I’ve yet to see a real world example of how it is somehow better
They developed new system calls (pledge and unveil) which restrict they system calls and file access of programs (here’s a good writeup by Andreas Kling after he added support in SerenityOS: https://awesomekling.github.io/pledge-and-unveil-in-SerenityOS/). As an example, the Firefox port for OpenBSD uses them to heavily restrict what random websites can do or get from your system.
Just one example since you’ve somehow yet to see any.
https://isopenbsdsecu.re/
I don’t think much changed since then, but would love to be proven wrong.Did you read it? The author is clearly biased against OpenBSD.
As an example, he dedicates quite a lot to talk about “ROP gadgets removal” (which is an ineffective mitigation employed by OpenBSD), however he also states:
Anyway, removing ROP gadgets the way OpenBSD is doing it doesn’t add a large amount of complexity, doesn’t harm performances nor debuggability, so why not, but it doesn’t make exploitation significantly harder, at all.
When you consider the fact that some mitigations which were considered overkill were proven significant with time (for example, OpenBSD was completely unaffected by Spectre v1 and similar exploits since they disabled hyperthreading), statements like these make it clear to me that the author is biased.
Edit: This is not to say the website is deceptive, it’s just that it doesn’t provide a good analysis or comparison of the security of different systems IMO.
It just has security checks and randomization that makes it harder to compromise. The trade off is usually performance.
The Linux kernel varies between mainstream distros. For instance, I believe that Fedora goes for a more hardened configuration while Debian targets stability
If you want to learn more with some hands one experience try Gentoo
My question would be “how do hardening kargs differ from a hardened kernel”?
Kargs can be dynamically applied and work easily on immutable distros. Tbh a monolithic unhardened kernel is my biggest problem with immutable Distros, as changing that is quite drastic.
It really depends on what flags the hardened kernel has. You might get the same result with args or you may get something totally different.
If you want to learn more try Gentoo
I don’t think that project is maintained anymore, but at one point in time it used to add patches that were part of the Kernel Self Protection project. I believe those changes are now largely part of the mainline kernel.
I.e. it’s not different anymore.
EDIT: Looks like it’s still maintained.
It is maintained.
I stand corrected. Looks like it is.
The same as “anything-hardened” OS is. WTF. Next question.
Windows-hardened?
“Windows-hardened” is SteamOS at this point.
Uncle hard?
