aszlig 536feffc68 chromium: Fix userns patch for kernel 3.18.2. ... Writing the gid_map is already non-fatal, but the actual sandbox process still tries to setresgid() to nogroup (usually 65534). This however fails, because if user namespace sandboxing is present, the namespace doesn't have CAP_SETGID at this point. Fortunately, the effective GID is already 65534, so we just need to check whether the target gid matches and only(!) setresgid() if it doesn't. So if someone would run a SUID version of the sandbox, it would still work nonetheless without a negative impact on security. Fixes #5730, thanks to @wizeman for reporting and initial debugging. Signed-off-by: aszlig <aszlig@redmoonstudios.org>		2015-01-13 06:18:10 +01:00
..
source	chromium: Fix userns patch for kernel 3.18.2.	2015-01-13 06:18:10 +01:00
browser.nix	Update my maintainership	2014-11-29 02:15:39 +01:00
common.nix	kerberos: Use default kerberos instead of krb5	2014-12-30 00:05:12 -08:00
default.nix	chromium: enable cups by default	2014-12-07 14:56:18 +01:00
plugins.nix	Change occurrences of gcc to the more general cc	2014-12-26 11:06:21 -06:00
sandbox.nix	chromium: Update beta and dev to latest versions.	2014-04-20 17:45:24 +02:00
update.sh	chromium: Move update.sh back into the main path.	2014-04-20 17:45:25 +02:00