Linux Kernel Defence Map – Security Hardening Concepts
Report a link problem
Submission timeline
2007–2026One slot for every year since HN launched. Height is that year's peak points; orange marks a 100+ point or 50+ comment breakout. Select a bar to open its strongest thread.
First comments on top threads
HN comment orderThis is by the author of the very helpful kernel-hardening-checker: https://github.com/a13xp0p0v/kernel-hardening-checker An interesting tool for analyzing your personal kernel config file and pointing out areas for security improvement. It's more comprehensive than KSPP (https://kspp.github.io/) but sometimes goes a little too far, suggesting disabling kernel features you may actively use. Definitely worth trying!
Most security features are disabled by default (PAX, grsecurity, SELinux), and when distributions enable them, they are the first to go when admins encounter problems. It is then a chicken-and-egg problem when software fails in secure environments, those failures are not reported/fixed upstream but circumvented, and consequently security cannot be enabled across the board because tools break. I'd be curious if open source software would become more robust if by default the popular CI systems would enable features…
The first top-level comment from each of the four biggest threads, in HN’s own order. Excerpts are shortened; open a comment for full context.
- Breakout years
- 2
- Total points
- 268
- Total comments
- 49
100+ points or 50+ comments
reference only — not used in Hall rules or ranking
reference only — not used in Hall rules or ranking
Every submission
| Date | Title as submitted | By | Points | Comments |
|---|---|---|---|---|
| 2018-05-01 | Linux Kernel Defence Map | adulau | 2 | 0 |
| 2021-08-15 | Linux Kernel Defence MapFirst breakout | ingve | 107 | 29 |
| 2025-04-05 | Linux Kernel Defence Map – Security Hardening ConceptsBest thread · Latest 20+ point return | transpute | 159 | 20 |