From 5183e92e4fd8e1b1ca3a118e901d6d16e17d8b9d Mon Sep 17 00:00:00 2001 From: Alyssa Ross Date: Tue, 21 Jul 2020 23:38:31 +0000 Subject: feat(3p/nix): remove allow-unsafe-native-code-during-evaluation This formerly controlled access to builtins.exec and builtins.importNative, but both of those are gone now, so there's no need for this option any more. Change-Id: I6850cbd6be264fbfb1b209a60026dadbd0ba1232 Reviewed-on: https://cl.tvl.fyi/c/depot/+/1341 Reviewed-by: glittershark Tested-by: BuildkiteCI --- third_party/nix/src/libexpr/eval.hh | 5 ----- 1 file changed, 5 deletions(-) (limited to 'third_party') diff --git a/third_party/nix/src/libexpr/eval.hh b/third_party/nix/src/libexpr/eval.hh index 3a0ad8e126..199253bc45 100644 --- a/third_party/nix/src/libexpr/eval.hh +++ b/third_party/nix/src/libexpr/eval.hh @@ -331,11 +331,6 @@ struct InvalidPathError : EvalError { }; struct EvalSettings : Config { - Setting enableNativeCode{this, false, - "allow-unsafe-native-code-during-evaluation", - "Whether builtin functions that allow " - "executing native code should be enabled."}; - Setting restrictEval{ this, false, "restrict-eval", "Whether to restrict file system access to paths in $NIX_PATH, " -- cgit 1.4.1