2016-02-27 15:33:18 +00:00
|
|
|
{ stdenv, fetchurl, pkgs }:
|
2009-12-14 15:28:55 +00:00
|
|
|
|
|
|
|
|
let
|
|
|
|
|
|
2011-03-21 15:53:22 +00:00
|
|
|
makeTuxonicePatch = { version, kernelVersion, sha256,
|
2013-11-19 20:36:55 +00:00
|
|
|
url ? "http://tuxonice.nigelcunningham.com.au/downloads/all/tuxonice-for-linux-${kernelVersion}-${version}.patch.bz2" }:
|
2011-03-21 15:53:22 +00:00
|
|
|
{ name = "tuxonice-${kernelVersion}";
|
|
|
|
|
patch = stdenv.mkDerivation {
|
|
|
|
|
name = "tuxonice-${version}-for-${kernelVersion}.patch";
|
|
|
|
|
src = fetchurl {
|
|
|
|
|
inherit url sha256;
|
|
|
|
|
};
|
|
|
|
|
phases = [ "installPhase" ];
|
|
|
|
|
installPhase = ''
|
|
|
|
|
source $stdenv/setup
|
|
|
|
|
bunzip2 -c $src > $out
|
|
|
|
|
'';
|
|
|
|
|
};
|
|
|
|
|
};
|
|
|
|
|
|
2016-02-28 03:10:59 +00:00
|
|
|
grsecPatch = { grversion ? "3.1", kernel, patches, kversion, revision, branch ? "test", sha256 }:
|
2016-02-27 15:33:18 +00:00
|
|
|
assert kversion == kernel.version;
|
nixos: add grsecurity module (#1875)
This module implements a significant refactoring in grsecurity
configuration for NixOS, making it far more usable by default and much
easier to configure.
- New security.grsecurity NixOS attributes.
- All grsec kernels supported
- Allows default 'auto' grsec configuration, or custom config
- Supports custom kernel options through kernelExtraConfig
- Defaults to high-security - user must choose kernel, server/desktop
mode, and any virtualisation software. That's all.
- kptr_restrict is fixed under grsecurity (it's unwriteable)
- grsecurity patch creation is now significantly abstracted
- only need revision, version, and SHA1
- kernel version requirements are asserted for sanity
- built kernels can have the uname specify the exact grsec version
for development or bug reports. Off by default (requires
`security.grsecurity.config.verboseVersion = true;`)
- grsecurity sysctl support
- By default, disabled.
- For people who enable it, NixOS deploys a 'grsec-lock' systemd
service which runs at startup. You are expected to configure sysctl
through NixOS like you regularly would, which will occur before the
service is started. As a result, changing sysctl settings requires
a reboot.
- New default group: 'grsecurity'
- Root is a member by default
- GRKERNSEC_PROC_GID is implicitly set to the 'grsecurity' GID,
making it possible to easily add users to this group for /proc
access
- AppArmor is now automatically enabled where it wasn't before, despite
implying features.apparmor = true
The most trivial example of enabling grsecurity in your kernel is by
specifying:
security.grsecurity.enable = true;
security.grsecurity.testing = true; # testing 3.13 kernel
security.grsecurity.config.system = "desktop"; # or "server"
This specifies absolutely no virtualisation support. In general, you
probably at least want KVM host support, which is a little more work.
So:
security.grsecurity.enable = true;
security.grsecurity.stable = true; # enable stable 3.2 kernel
security.grsecurity.config = {
system = "server";
priority = "security";
virtualisationConfig = "host";
virtualisationSoftware = "kvm";
hardwareVirtualisation = true;
}
This module has primarily been tested on Hetzner EX40 & VQ7 servers
using NixOps.
Signed-off-by: Austin Seipp <aseipp@pobox.com>
2014-04-06 19:18:12 +00:00
|
|
|
{ name = "grsecurity-${grversion}-${kversion}";
|
2016-02-27 18:54:55 +00:00
|
|
|
inherit grversion kernel patches kversion revision;
|
2016-05-14 03:05:08 +00:00
|
|
|
# When updating versions/hashes, ALWAYS use the official version; we use
|
|
|
|
|
# this mirror only because upstream removes sources files immediately upon
|
|
|
|
|
# releasing a new version ...
|
nixos: add grsecurity module (#1875)
This module implements a significant refactoring in grsecurity
configuration for NixOS, making it far more usable by default and much
easier to configure.
- New security.grsecurity NixOS attributes.
- All grsec kernels supported
- Allows default 'auto' grsec configuration, or custom config
- Supports custom kernel options through kernelExtraConfig
- Defaults to high-security - user must choose kernel, server/desktop
mode, and any virtualisation software. That's all.
- kptr_restrict is fixed under grsecurity (it's unwriteable)
- grsecurity patch creation is now significantly abstracted
- only need revision, version, and SHA1
- kernel version requirements are asserted for sanity
- built kernels can have the uname specify the exact grsec version
for development or bug reports. Off by default (requires
`security.grsecurity.config.verboseVersion = true;`)
- grsecurity sysctl support
- By default, disabled.
- For people who enable it, NixOS deploys a 'grsec-lock' systemd
service which runs at startup. You are expected to configure sysctl
through NixOS like you regularly would, which will occur before the
service is started. As a result, changing sysctl settings requires
a reboot.
- New default group: 'grsecurity'
- Root is a member by default
- GRKERNSEC_PROC_GID is implicitly set to the 'grsecurity' GID,
making it possible to easily add users to this group for /proc
access
- AppArmor is now automatically enabled where it wasn't before, despite
implying features.apparmor = true
The most trivial example of enabling grsecurity in your kernel is by
specifying:
security.grsecurity.enable = true;
security.grsecurity.testing = true; # testing 3.13 kernel
security.grsecurity.config.system = "desktop"; # or "server"
This specifies absolutely no virtualisation support. In general, you
probably at least want KVM host support, which is a little more work.
So:
security.grsecurity.enable = true;
security.grsecurity.stable = true; # enable stable 3.2 kernel
security.grsecurity.config = {
system = "server";
priority = "security";
virtualisationConfig = "host";
virtualisationSoftware = "kvm";
hardwareVirtualisation = true;
}
This module has primarily been tested on Hetzner EX40 & VQ7 servers
using NixOps.
Signed-off-by: Austin Seipp <aseipp@pobox.com>
2014-04-06 19:18:12 +00:00
|
|
|
patch = fetchurl {
|
2016-05-14 03:05:08 +00:00
|
|
|
url = "https://raw.githubusercontent.com/slashbeast/grsecurity-scrape/master/test/grsecurity-${grversion}-${kversion}-${revision}.patch";
|
nixos: add grsecurity module (#1875)
This module implements a significant refactoring in grsecurity
configuration for NixOS, making it far more usable by default and much
easier to configure.
- New security.grsecurity NixOS attributes.
- All grsec kernels supported
- Allows default 'auto' grsec configuration, or custom config
- Supports custom kernel options through kernelExtraConfig
- Defaults to high-security - user must choose kernel, server/desktop
mode, and any virtualisation software. That's all.
- kptr_restrict is fixed under grsecurity (it's unwriteable)
- grsecurity patch creation is now significantly abstracted
- only need revision, version, and SHA1
- kernel version requirements are asserted for sanity
- built kernels can have the uname specify the exact grsec version
for development or bug reports. Off by default (requires
`security.grsecurity.config.verboseVersion = true;`)
- grsecurity sysctl support
- By default, disabled.
- For people who enable it, NixOS deploys a 'grsec-lock' systemd
service which runs at startup. You are expected to configure sysctl
through NixOS like you regularly would, which will occur before the
service is started. As a result, changing sysctl settings requires
a reboot.
- New default group: 'grsecurity'
- Root is a member by default
- GRKERNSEC_PROC_GID is implicitly set to the 'grsecurity' GID,
making it possible to easily add users to this group for /proc
access
- AppArmor is now automatically enabled where it wasn't before, despite
implying features.apparmor = true
The most trivial example of enabling grsecurity in your kernel is by
specifying:
security.grsecurity.enable = true;
security.grsecurity.testing = true; # testing 3.13 kernel
security.grsecurity.config.system = "desktop"; # or "server"
This specifies absolutely no virtualisation support. In general, you
probably at least want KVM host support, which is a little more work.
So:
security.grsecurity.enable = true;
security.grsecurity.stable = true; # enable stable 3.2 kernel
security.grsecurity.config = {
system = "server";
priority = "security";
virtualisationConfig = "host";
virtualisationSoftware = "kvm";
hardwareVirtualisation = true;
}
This module has primarily been tested on Hetzner EX40 & VQ7 servers
using NixOps.
Signed-off-by: Austin Seipp <aseipp@pobox.com>
2014-04-06 19:18:12 +00:00
|
|
|
inherit sha256;
|
|
|
|
|
};
|
|
|
|
|
features.grsecurity = true;
|
2013-05-11 05:44:30 +00:00
|
|
|
};
|
nixos: add grsecurity module (#1875)
This module implements a significant refactoring in grsecurity
configuration for NixOS, making it far more usable by default and much
easier to configure.
- New security.grsecurity NixOS attributes.
- All grsec kernels supported
- Allows default 'auto' grsec configuration, or custom config
- Supports custom kernel options through kernelExtraConfig
- Defaults to high-security - user must choose kernel, server/desktop
mode, and any virtualisation software. That's all.
- kptr_restrict is fixed under grsecurity (it's unwriteable)
- grsecurity patch creation is now significantly abstracted
- only need revision, version, and SHA1
- kernel version requirements are asserted for sanity
- built kernels can have the uname specify the exact grsec version
for development or bug reports. Off by default (requires
`security.grsecurity.config.verboseVersion = true;`)
- grsecurity sysctl support
- By default, disabled.
- For people who enable it, NixOS deploys a 'grsec-lock' systemd
service which runs at startup. You are expected to configure sysctl
through NixOS like you regularly would, which will occur before the
service is started. As a result, changing sysctl settings requires
a reboot.
- New default group: 'grsecurity'
- Root is a member by default
- GRKERNSEC_PROC_GID is implicitly set to the 'grsecurity' GID,
making it possible to easily add users to this group for /proc
access
- AppArmor is now automatically enabled where it wasn't before, despite
implying features.apparmor = true
The most trivial example of enabling grsecurity in your kernel is by
specifying:
security.grsecurity.enable = true;
security.grsecurity.testing = true; # testing 3.13 kernel
security.grsecurity.config.system = "desktop"; # or "server"
This specifies absolutely no virtualisation support. In general, you
probably at least want KVM host support, which is a little more work.
So:
security.grsecurity.enable = true;
security.grsecurity.stable = true; # enable stable 3.2 kernel
security.grsecurity.config = {
system = "server";
priority = "security";
virtualisationConfig = "host";
virtualisationSoftware = "kvm";
hardwareVirtualisation = true;
}
This module has primarily been tested on Hetzner EX40 & VQ7 servers
using NixOps.
Signed-off-by: Austin Seipp <aseipp@pobox.com>
2014-04-06 19:18:12 +00:00
|
|
|
|
2009-12-14 15:28:55 +00:00
|
|
|
in
|
|
|
|
|
|
2011-07-11 13:59:40 +00:00
|
|
|
rec {
|
2009-12-14 15:28:55 +00:00
|
|
|
|
2016-03-25 09:50:08 +00:00
|
|
|
link_lguest =
|
|
|
|
|
{ name = "gcc5-link-lguest";
|
|
|
|
|
patch = ./gcc5-link-lguest.patch;
|
|
|
|
|
};
|
|
|
|
|
|
|
|
|
|
link_apm =
|
|
|
|
|
{ name = "gcc5-link-apm";
|
|
|
|
|
patch = ./gcc5-link-apm.patch;
|
|
|
|
|
};
|
|
|
|
|
|
2015-01-13 23:49:14 +00:00
|
|
|
bridge_stp_helper =
|
|
|
|
|
{ name = "bridge-stp-helper";
|
|
|
|
|
patch = ./bridge-stp-helper.patch;
|
|
|
|
|
};
|
|
|
|
|
|
2010-07-18 21:10:46 +00:00
|
|
|
no_xsave =
|
|
|
|
|
{ name = "no-xsave";
|
2012-07-02 14:16:27 +00:00
|
|
|
patch = ./no-xsave.patch;
|
2010-07-18 21:10:46 +00:00
|
|
|
features.noXsave = true;
|
2010-06-20 20:52:08 +00:00
|
|
|
};
|
2010-07-25 12:15:59 +00:00
|
|
|
|
2012-06-16 10:49:03 +00:00
|
|
|
mips_fpureg_emu =
|
|
|
|
|
{ name = "mips-fpureg-emulation";
|
|
|
|
|
patch = ./mips-fpureg-emulation.patch;
|
|
|
|
|
};
|
|
|
|
|
|
|
|
|
|
mips_fpu_sigill =
|
|
|
|
|
{ name = "mips-fpu-sigill";
|
|
|
|
|
patch = ./mips-fpu-sigill.patch;
|
|
|
|
|
};
|
|
|
|
|
|
2012-11-05 23:16:13 +00:00
|
|
|
mips_ext3_n32 =
|
|
|
|
|
{ name = "mips-ext3-n32";
|
|
|
|
|
patch = ./mips-ext3-n32.patch;
|
|
|
|
|
};
|
|
|
|
|
|
2016-04-09 23:36:02 +00:00
|
|
|
ubuntu_fan_4_4 =
|
2015-08-09 23:13:40 +00:00
|
|
|
{ name = "ubuntu-fan";
|
2016-04-09 23:36:02 +00:00
|
|
|
patch = ./ubuntu-fan-4.4.patch;
|
2015-08-09 23:13:40 +00:00
|
|
|
};
|
|
|
|
|
|
2015-09-25 21:42:16 +00:00
|
|
|
ubuntu_unprivileged_overlayfs =
|
|
|
|
|
{ name = "ubuntu-unprivileged-overlayfs";
|
|
|
|
|
patch = ./ubuntu-unprivileged-overlayfs.patch;
|
|
|
|
|
};
|
|
|
|
|
|
2013-11-19 20:36:55 +00:00
|
|
|
tuxonice_3_10 = makeTuxonicePatch {
|
|
|
|
|
version = "2013-11-07";
|
|
|
|
|
kernelVersion = "3.10.18";
|
|
|
|
|
sha256 = "00b1rqgd4yr206dxp4mcymr56ymbjcjfa4m82pxw73khj032qw3j";
|
|
|
|
|
};
|
|
|
|
|
|
2016-05-15 19:36:24 +00:00
|
|
|
grsecurity_3_14 = throw "grsecurity stable is no longer supported";
|
2013-07-22 19:44:31 +00:00
|
|
|
|
2016-05-15 19:36:24 +00:00
|
|
|
grsecurity_4_4 = throw "grsecurity stable is no longer supported";
|
2013-11-26 22:08:51 +00:00
|
|
|
|
2016-05-02 05:06:36 +00:00
|
|
|
grsecurity_4_5 = grsecPatch
|
|
|
|
|
{ kernel = pkgs.grsecurity_base_linux_4_5;
|
|
|
|
|
patches = [ grsecurity_fix_path_4_5 ];
|
2016-06-07 13:04:24 +00:00
|
|
|
kversion = "4.5.6";
|
|
|
|
|
revision = "201606051644";
|
|
|
|
|
sha256 = "1ympym3kpaychd1qsb10hn5ffv8w83ccfmb631hj4jk69xwrry9m";
|
2016-05-02 05:06:36 +00:00
|
|
|
};
|
|
|
|
|
|
|
|
|
|
grsecurity_latest = grsecurity_4_5;
|
2016-02-28 03:10:59 +00:00
|
|
|
|
2016-05-02 05:06:36 +00:00
|
|
|
grsecurity_fix_path_4_5 =
|
|
|
|
|
{ name = "grsecurity-fix-path-4.5";
|
|
|
|
|
patch = ./grsecurity-path-4.5.patch;
|
|
|
|
|
};
|
|
|
|
|
|
2015-02-10 12:45:20 +00:00
|
|
|
crc_regression =
|
|
|
|
|
{ name = "crc-backport-regression";
|
|
|
|
|
patch = ./crc-regression.patch;
|
|
|
|
|
};
|
2015-04-08 12:13:42 +00:00
|
|
|
|
2016-01-10 19:07:45 +00:00
|
|
|
genksyms_fix_segfault =
|
|
|
|
|
{ name = "genksyms-fix-segfault";
|
|
|
|
|
patch = ./genksyms-fix-segfault.patch;
|
|
|
|
|
};
|
|
|
|
|
|
|
|
|
|
|
2016-01-10 19:10:11 +00:00
|
|
|
chromiumos_Kconfig_fix_entries_3_14 =
|
|
|
|
|
{ name = "Kconfig_fix_entries_3_14";
|
|
|
|
|
patch = ./chromiumos-patches/fix-double-Kconfig-entry-3.14.patch;
|
|
|
|
|
};
|
|
|
|
|
|
2016-01-10 19:07:45 +00:00
|
|
|
chromiumos_Kconfig_fix_entries_3_18 =
|
|
|
|
|
{ name = "Kconfig_fix_entries_3_18";
|
|
|
|
|
patch = ./chromiumos-patches/fix-double-Kconfig-entry-3.18.patch;
|
|
|
|
|
};
|
|
|
|
|
|
|
|
|
|
chromiumos_no_link_restrictions =
|
|
|
|
|
{ name = "chromium-no-link-restrictions";
|
|
|
|
|
patch = ./chromiumos-patches/no-link-restrictions.patch;
|
|
|
|
|
};
|
2016-01-10 19:10:11 +00:00
|
|
|
|
|
|
|
|
chromiumos_mfd_fix_dependency =
|
|
|
|
|
{ name = "mfd_fix_dependency";
|
|
|
|
|
patch = ./chromiumos-patches/mfd-fix-dependency.patch;
|
|
|
|
|
};
|
2016-04-12 18:30:14 +00:00
|
|
|
qat_common_Makefile =
|
|
|
|
|
{ name = "qat_common_Makefile";
|
|
|
|
|
patch = ./qat_common_Makefile.patch;
|
|
|
|
|
};
|
2009-12-14 15:28:55 +00:00
|
|
|
}
|
