diff options
author | Daniel Peebles <pumpkin@me.com> | 2015-01-15 02:49:21 -0500 |
---|---|---|
committer | Shea Levy <shea@shealevy.com> | 2015-01-18 23:25:29 -0500 |
commit | f46e329a1332738694973d67d70dc5e32c5eda40 (patch) | |
tree | 885dc0845b67cec1ca00c0d3dcc0336b43808eaf /src | |
parent | f6716e95bb5ea6fc267f228880b46e9509fc4801 (diff) |
Make inputs writeable in the sandbox (builds still can’t actually write due to user permissions)
Diffstat (limited to 'src')
-rw-r--r-- | src/libstore/build.cc | 9 |
1 files changed, 7 insertions, 2 deletions
diff --git a/src/libstore/build.cc b/src/libstore/build.cc index 5285d39df..e0398e2fb 100644 --- a/src/libstore/build.cc +++ b/src/libstore/build.cc @@ -2271,8 +2271,13 @@ void DerivationGoal::runChild() } sandboxProfile += ")\n"; - /* Our inputs (transitive dependencies and any impurities computed above) */ - sandboxProfile += "(allow file-read* process-exec\n"; + /* Our inputs (transitive dependencies and any impurities computed above) + Note that the sandbox profile allows file-write* even though it isn't seemingly necessary. First of all, nix's standard user permissioning + mechanism still prevents builders from writing to input directories, so no security/purity is lost. The reason we allow file-write* is that + denying it means the `access` syscall will return EPERM instead of EACCESS, which confuses a few programs that assume (understandably, since + it appears to be a violation of the POSIX spec) that `access` won't do that, and don't deal with it nicely if it does. The most notable of + these is the entire GHC Haskell ecosystem. */ + sandboxProfile += "(allow file-read* file-write* process-exec\n"; for (auto & i : dirsInChroot) { if (i.first != i.second) throw SysError(format("can't map '%1%' to '%2%': mismatched impure paths not supported on darwin")); |