Revision df716c98d203ab64cdf05f9c17fdae565b7daa1c authored by Eelco Dolstra on 23 June 2012, 04:28:35 UTC, committed by Eelco Dolstra on 23 June 2012, 04:28:35 UTC
On Linux it's possible to run a process in its own network namespace, meaning that it gets its own set of network interfaces, disjunct from the rest of the system. We use this to completely remove network access to chroot builds, except that they get a private loopback interface. This means that: - Builders cannot connect to the outside network or to other processes on the same machine, except processes within the same build. - Vice versa, other processes cannot connect to processes in a chroot build, and open ports/connections do not show up in "netstat". - If two concurrent builders try to listen on the same port (e.g. as part of a test), they no longer conflict with each other. This was inspired by the "PrivateNetwork" flag in systemd.
1 parent 2f3f413
| File | Mode | Size |
|---|---|---|
| corepkgs | ||
| doc | ||
| misc | ||
| perl | ||
| scripts | ||
| src | ||
| tests | ||
| .gitignore | -rw-r--r-- | 2.5 KB |
| AUTHORS | -rw-r--r-- | 149 bytes |
| COPYING | -rw-r--r-- | 25.8 KB |
| INSTALL | -rw-r--r-- | 9.0 KB |
| Makefile.am | -rw-r--r-- | 1.7 KB |
| README | -rw-r--r-- | 360 bytes |
| bootstrap.sh | -rwxr-xr-x | 68 bytes |
| build.nix | -rw-r--r-- | 4.8 KB |
| configure.ac | -rw-r--r-- | 9.2 KB |
| nix.conf.example | -rw-r--r-- | 7.2 KB |
| nix.spec.in | -rw-r--r-- | 5.7 KB |
| release.nix | -rw-r--r-- | 7.8 KB |
| substitute.mk | -rw-r--r-- | 1.2 KB |
| version | -rw-r--r-- | 3 bytes |
Computing file changes ...
README
Loading README ...
