Joachim Fasting e99228db30
grsecurity module: force a known good kernel package set
Previously, we would only set a default value, on the theory that
`boot.kernelPackages` could be used to sanely configure a custom grsec
kernel.  Regrettably, this is not the case and users who expect e.g.,
`boot.kernelPackages = pkgs.linuxPackages_latest` to work will end up
with a non-grsec kernel (this problem has come up twice on the bug
tracker recently).

With this patch, `security.grsecurity.enable = true` implies
`boot.kernelPackages = linuxPackages_grsec_nixos` and any customization
must be done via package override or by eschewing the module.
2016-11-28 12:11:04 +01:00
..
2016-10-03 19:31:42 +02:00
2015-07-15 12:40:06 +02:00
2016-10-09 02:00:18 +02:00
2016-11-16 22:36:05 +09:00
2016-02-25 13:52:45 +00:00
2015-09-18 18:48:50 +00:00